Bug #16396
release_process: consider adding --img to the idf-content call
100%
Description
Spotted while preparing the 3.12 release, the following call in release_process.mdwn
:
./bin/idf-content \
--version "${VERSION:?}" \
--iso "${ISO_PATH:?}" \
> "${RELEASE_CHECKOUT:?}"/wiki/src/install/v2/Tails/amd64/stable/latest.json && \
cat > "${RELEASE_CHECKOUT:?}"/wiki/src/install/v1/Tails/amd64/stable/latest.yml <<EOF
[…]
After discussion with anonym (who looked at the image verification code, if I got this right), we decided to add a --img
option for the latest.json
file.
We should probably decide whether to revert that (amending the latest.json
file); or to keep it and amend the documentation.
(There’s also latest.yml
which wasn’t modified, but I suppose this was for v1 and need to stay the same, while v2 lets us have several images?)
Subtasks
History
#1 Updated by anonym 2019-01-29 14:01:20
u confirmed that —img should be added just like we suspected. I have fixed it in a local commit to testing that I’ll push once we’re allowed to.
#2 Updated by intrigeri 2019-01-29 14:45:16
> (There’s also latest.yml
which wasn’t modified, but I suppose this was for v1 and need to stay the same, while v2 lets us have several images?)
Yes, see the updated design doc in wiki/src/contribute/design/verification_extension.mdwn :)
#3 Updated by Anonymous 2019-01-29 17:37:32
super cool you thought about that!
#4 Updated by anonym 2019-01-29 18:15:39
- Status changed from Confirmed to Fix committed
- % Done changed from 0 to 100
Applied in changeset commit:tails|dc5e2e97249f2fb58b34e77c7292595a1b44376a.
#5 Updated by anonym 2019-02-13 08:27:13
- Status changed from Fix committed to Resolved
- Assignee deleted (
anonym) - Target version set to Tails_3.12.1
- QA Check set to Pass