On Mon, 20 Jul 2020 18:08:09 +0200 Denis 'GNUtoo' Carikli <[email protected]> wrote:
This needs part needs to be replaced: > +Releasing the images: > +--------------------- > +When the build is done, you can finally use the the release.sh > script to +populate the final directory with all the files to > release. + > +You can then push that directory to the FTP server and run the FTP > server +trigger script when all the files have been copied. By the following: > Releasing the images: > --------------------- > When the build is done, you can finally use the the release.sh script > to populate the final directory with all the files to release. > > For instance for releasing Replicant 6.0 0004 RC2 I used the > following: $ release.sh replicant-6.0 replicant-6.0-0004-rc2 > > The replicant-6.0 directory contained the Replicant source code and > replicant-6.0-0004-rc2 was an empty directory. > > This script can take a long time if the connection to your builder is > slow, as this downloads all the images. > > You need to sign the images with the release.sh script. I used the > following for the replicant-6.0-0004-rc2 release: > $ release.sh replicant-6.0 replicant-6.0-0004-rc2 signatures > > The signature is done as a separate process to enable use cases where > the connection to the build server is slow and gpg is setup to be run > interactively (for instance by typing a password). > > You can then push that directory to the FTP server and run the FTP > server trigger script when all the files have been copied. Else the images won't be signed. At first I also forgot to sign the replicant-6.0-0004-rc2 images and pushed them to the FTP as is. I've now signed them as well and the FTP should now have the signature as well. Denis.
pgpmSGzZVw9d9.pgp
Description: OpenPGP digital signature
_______________________________________________ Replicant mailing list [email protected] https://lists.osuosl.org/mailman/listinfo/replicant
