diff options
| author | Denis 'GNUtoo' Carikli <GNUtoo@cyberdimension.org> | 2020-10-24 02:10:19 +0200 |
|---|---|---|
| committer | Denis 'GNUtoo' Carikli <GNUtoo@cyberdimension.org> | 2020-10-24 02:27:13 +0200 |
| commit | 2ee4f8df327e34a7a213cbe09e444adb32607a9b (patch) | |
| tree | 1d14b8d662b3675b1ed45b7f825127600a9f2785 /releasevars.sh | |
| parent | 0f27d50b2a929ab3f2b25e89f1b01fa1a9984782 (diff) | |
| download | vendor_replicant-release-scripts-2ee4f8df327e34a7a213cbe09e444adb32607a9b.tar.gz vendor_replicant-release-scripts-2ee4f8df327e34a7a213cbe09e444adb32607a9b.tar.bz2 vendor_replicant-release-scripts-2ee4f8df327e34a7a213cbe09e444adb32607a9b.zip | |
Release procedure: Add information about key handling
Before, during and after a release, we need to manage signing keys:
- We might need to take care of keeping the gpg signing key still
valid (not expired) for some time after the release.
- We also may need to migrate from one set of keys generated during
the build process to a new one.
Signed-off-by: Denis 'GNUtoo' Carikli <GNUtoo@cyberdimension.org>
Diffstat (limited to 'releasevars.sh')
| -rwxr-xr-x | releasevars.sh | 11 |
1 files changed, 10 insertions, 1 deletions
diff --git a/releasevars.sh b/releasevars.sh index 896d4f8..d3c7f59 100755 --- a/releasevars.sh +++ b/releasevars.sh @@ -67,7 +67,16 @@ RELEASE_DEVICES="\ n5110 \ " -RELEASE_KEY="FB31DBA3AB8DB76A4157329F7651568F80374459" +RELEASE_KEY="" +if [ -z "${RELEASE_KEY}" ] ; then + echo "You need to define the RELEASE_KEY variable in the releasevars.sh script." + echo "This variable contains the gpg key that will sign the images you are releasing." + echo + echo "For example:" + echo " RELEASE_KEY=\"FB31DBA3AB8DB76A4157329F7651568F80374459\"" + exit 1 +fi + REPO="repo" COLOR=1 |