[Replicant] build broken

[Fil Lupin]

A word : I suggest to generate image and recovery with names including the replicant version and device. I will create more clear images if we store several images (of course, each one can rename it as wanted currently so this is not a real issue).

For example, for GT-I9300, image would be named replicant-6.0-0003-i9300.zip and recovery named recovery-6.0-0003-i9300.img

Regards,

- Fil Lupin.

‐‐‐‐‐‐‐ Original Message ‐‐‐‐‐‐‐
On Wednesday, March 6, 2019 6:54 AM, Fil Lupin <fillupin at protonmail.com> wrote:

> Hi,
> thank you Denis, I found in parallel a way to solve it by deleting this directory.
> I gave the way in the topic and modify the topic to inform it is solved.
> Thank you for your answer,
>
> -   Fil Lupin.
>
>     Sent with ProtonMail Secure Email.
>
>     ‐‐‐‐‐‐‐ Original Message ‐‐‐‐‐‐‐
>     On Wednesday, March 6, 2019 12:49 AM, Denis 'GNUtoo' Carikli GNUtoo at cyberdimension.org wrote:
>
>
> > On Sun, 03 Mar 2019 11:31:45 +0000
> > Fil Lupin fillupin at protonmail.com wrote:
> >
> > > Hello,
> >
> > Hi,
> >
> > > I recently tried to build a new replicant, and I got an error "ERROR:
> > > signapk.jar failed: return code 1" when launching
> > > "./vendor/replicant/sign-build i9300" I precise that I tried to
> > > delete keys with "rm -r vendor/replicant-security" as specified in
> > > https://redmine.replicant.us/projects/replicant/wiki/BuildTips but I
> > > get the same error when launching again
> > > "./vendor/replicant/sign-build i9300"
> > > I gave details in topic
> > > https://redmine.replicant.us/boards/15/topics/15111
> > > Does anyone already encountered this behaviout and know how to solve
> > > it?
> >
> > Yes,
> > I've just merged doak's patches that make the process more robust.
> > I still had to do an "rm -r vendor/replicant-security" before retrying
> > though, but with the patches it worked.
> > Denis.
>
> Replicant mailing list
> Replicant at osuosl.org
> https://lists.osuosl.org/mailman/listinfo/replicant