UDF generation is broken for release candidates
When preparing Tails 4.11~rc1 I encountered problems in the "Prepare upgrade-description files" section of the release process. After running tails-iuk-generate-upgrade-description-files
I had these updated files:
modified: wiki/src/upgrade/v2/Tails/4.0/amd64/stable/upgrades.yml
modified: wiki/src/upgrade/v2/Tails/4.0~beta1/amd64/alpha/upgrades.yml
modified: wiki/src/upgrade/v2/Tails/4.0~beta1/amd64/stable/upgrades.yml
modified: wiki/src/upgrade/v2/Tails/4.0~beta2/amd64/alpha/upgrades.yml
modified: wiki/src/upgrade/v2/Tails/4.0~beta2/amd64/stable/upgrades.yml
modified: wiki/src/upgrade/v2/Tails/4.0~rc1/amd64/alpha/upgrades.yml
modified: wiki/src/upgrade/v2/Tails/4.0~rc1/amd64/stable/upgrades.yml
modified: wiki/src/upgrade/v2/Tails/4.1.1/amd64/stable/upgrades.yml
modified: wiki/src/upgrade/v2/Tails/4.1/amd64/stable/upgrades.yml
modified: wiki/src/upgrade/v2/Tails/4.10/amd64/stable/upgrades.yml
modified: wiki/src/upgrade/v2/Tails/4.2.2/amd64/stable/upgrades.yml
modified: wiki/src/upgrade/v2/Tails/4.2/amd64/stable/upgrades.yml
modified: wiki/src/upgrade/v2/Tails/4.3/amd64/stable/upgrades.yml
modified: wiki/src/upgrade/v2/Tails/4.4.1/amd64/stable/upgrades.yml
modified: wiki/src/upgrade/v2/Tails/4.4/amd64/stable/upgrades.yml
modified: wiki/src/upgrade/v2/Tails/4.5/amd64/stable/upgrades.yml
modified: wiki/src/upgrade/v2/Tails/4.5~rc1/amd64/alpha/upgrades.yml
modified: wiki/src/upgrade/v2/Tails/4.5~rc1/amd64/stable/upgrades.yml
modified: wiki/src/upgrade/v2/Tails/4.6/amd64/stable/upgrades.yml
modified: wiki/src/upgrade/v2/Tails/4.7/amd64/stable/upgrades.yml
modified: wiki/src/upgrade/v2/Tails/4.8/amd64/stable/upgrades.yml
modified: wiki/src/upgrade/v2/Tails/4.9/amd64/stable/upgrades.yml
Note how there are only a few updates on the alpha
channel. I had to manually copy the stable
channel's files into the alpha
channel and fix them up (setting channel: alpha
).
And while we are changing this section we might as well change the instructions for the test
channel so it only creates one UDF, for ${PREVIOUS_VERSION}
, since that's all we'll manually test any way (IMHO RMs are having enough fun typing their OpenPGP smartcard passphrase repeatedly for each updated stable/alpha UDF signature already :)).
To upload designs, you'll need to enable LFS and have admin enable hashed storage. More information