Bug #17419

Please check the result of tails-iuk-generate-upgrade-description-files

Added by CyrilBrulebois 2020-01-10 02:07:48 . Updated 2020-01-14 10:49:59 .

Status:
Resolved
Priority:
Urgent
Assignee:
CyrilBrulebois
Category:
Target version:
Tails_4.2.2
Start date:
Due date:
% Done:

0%

Feature Branch:
Type of work:
Research
Blueprint:

Starter:
Affected tool:
Deliverable for:

Description

kibi@armor:~/work/clients/tails/release/release-checkout$ ${RELEASE_CHECKOUT:?}/config/chroot_local-includes/usr/src/iuk/bin/tails-iuk-generate-upgrade-description-files \
>             --version "${VERSION:?}" \
>             $( \
>                 if [ "${DIST:?}" = stable ]; then
>                     echo \
>                         --next_version "${NEXT_PLANNED_MAJOR_VERSION:?}" \
>                         --next_version "${NEXT_PLANNED_MAJOR_VERSION:?}~rc1" \
>                         --next_version "${NEXT_PLANNED_BUGFIX_VERSION:?}" \
>                         --next_version "${NEXT_POTENTIAL_EMERGENCY_VERSION:?}"
>                 else
>                     echo --next_version $(echo ${VERSION:?} | sed -e 's,~.*$,,')
>                 fi
>             ) \
>             $( \
>                 for version in $(echo ${IUK_SOURCE_VERSIONS:?}); do
>                    echo "--previous_version ${version:?}"
>                 done \
>             ) \
>             --iso "${ISO_PATH:?}" \
>             --iuks "${ISOS:?}" \
>             --release_checkout "${RELEASE_CHECKOUT:?}" \
>             --major_release "${MAJOR_RELEASE:?}" \
>             --channel "${DIST:?}"
* Creating upgrade-description files for new release (4.2.1), alpha channel: 
  /home/kibi/work/clients/tails/release/release-checkout/wiki/src/upgrade/v2/Tails/4.2.1/amd64/alpha/upgrades.yml ...

* Creating upgrade-description files for new release (4.2.1), stable channel: 
  /home/kibi/work/clients/tails/release/release-checkout/wiki/src/upgrade/v2/Tails/4.2.1/amd64/stable/upgrades.yml ...

* Creating upgrade-description files for next release (4.5), alpha channel: 
  /home/kibi/work/clients/tails/release/release-checkout/wiki/src/upgrade/v2/Tails/4.5/amd64/alpha/upgrades.yml ...

* Creating upgrade-description files for next release (4.5~rc1), alpha channel: 
  /home/kibi/work/clients/tails/release/release-checkout/wiki/src/upgrade/v2/Tails/4.5~rc1/amd64/alpha/upgrades.yml ...

* Creating upgrade-description files for next release (4.3), alpha channel: 
  /home/kibi/work/clients/tails/release/release-checkout/wiki/src/upgrade/v2/Tails/4.3/amd64/alpha/upgrades.yml ...

* Creating upgrade-description files for next release (4.2.2), alpha channel: 
  /home/kibi/work/clients/tails/release/release-checkout/wiki/src/upgrade/v2/Tails/4.2.2/amd64/alpha/upgrades.yml ...

* Creating upgrade-description files for next release (4.5), stable channel: 
  /home/kibi/work/clients/tails/release/release-checkout/wiki/src/upgrade/v2/Tails/4.5/amd64/stable/upgrades.yml ...

* Creating upgrade-description files for next release (4.5~rc1), stable channel: 
  /home/kibi/work/clients/tails/release/release-checkout/wiki/src/upgrade/v2/Tails/4.5~rc1/amd64/stable/upgrades.yml ...

* Creating upgrade-description files for next release (4.3), stable channel: 
  /home/kibi/work/clients/tails/release/release-checkout/wiki/src/upgrade/v2/Tails/4.3/amd64/stable/upgrades.yml ...

* Creating upgrade-description files for next release (4.2.2), stable channel: 
  /home/kibi/work/clients/tails/release/release-checkout/wiki/src/upgrade/v2/Tails/4.2.2/amd64/stable/upgrades.yml ...

* Updating upgrade-description file for previous release (4.0): 
  /home/kibi/work/clients/tails/release/release-checkout/wiki/src/upgrade/v2/Tails/4.0/amd64/stable/upgrades.yml ...
  Adding full upgrade...
  No IUK could be found for 4.0, we will only advertise full upgrade.

* Updating upgrade-description file for previous release (4.0~beta1): 
  /home/kibi/work/clients/tails/release/release-checkout/wiki/src/upgrade/v2/Tails/4.0~beta1/amd64/stable/upgrades.yml ...
  Adding full upgrade...
  No IUK could be found for 4.0~beta1, we will only advertise full upgrade.

* Updating upgrade-description file for previous release (4.0~beta2): 
  /home/kibi/work/clients/tails/release/release-checkout/wiki/src/upgrade/v2/Tails/4.0~beta2/amd64/stable/upgrades.yml ...
  Adding full upgrade...
  No IUK could be found for 4.0~beta2, we will only advertise full upgrade.

* Updating upgrade-description file for previous release (4.0~rc1): 
  /home/kibi/work/clients/tails/release/release-checkout/wiki/src/upgrade/v2/Tails/4.0~rc1/amd64/stable/upgrades.yml ...
  Adding full upgrade...
  No IUK could be found for 4.0~rc1, we will only advertise full upgrade.

* Updating upgrade-description file for previous release (4.1): 
  /home/kibi/work/clients/tails/release/release-checkout/wiki/src/upgrade/v2/Tails/4.1/amd64/stable/upgrades.yml ...
  Adding full upgrade...
  No IUK could be found for 4.1, we will only advertise full upgrade.

* Updating upgrade-description file for previous release (4.1.1): 
  /home/kibi/work/clients/tails/release/release-checkout/wiki/src/upgrade/v2/Tails/4.1.1/amd64/stable/upgrades.yml ...
  Adding full upgrade...
  No IUK could be found for 4.1.1, we will only advertise full upgrade.

* Updating upgrade-description file for previous release (4.2): 
  /home/kibi/work/clients/tails/release/release-checkout/wiki/src/upgrade/v2/Tails/4.2/amd64/stable/upgrades.yml ...
  Adding full upgrade...
  No IUK could be found for 4.2, we will only advertise full upgrade.

I’m worried about all those “No IUK could be found for ” while we’ve just went through the troubles of building+verifying them…

On the git side:

kibi@armor:~/work/clients/tails/release/release-checkout$ git status
On branch web/release-4.2.1
Your branch is up-to-date with 'origin/web/release-4.2.1'.
Changes not staged for commit:
  (use "git add <file>..." to update what will be committed)
  (use "git checkout -- <file>..." to discard changes in working directory)

    modified:   wiki/src/upgrade/v2/Tails/4.0/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.2/amd64/stable/upgrades.yml
    modified:   wiki/src/upgrade/v2/Tails/4.3/amd64/alpha/upgrades.yml
    modified:   wiki/src/upgrade/v2/Tails/4.3/amd64/stable/upgrades.yml
    modified:   wiki/src/upgrade/v2/Tails/4.5/amd64/alpha/upgrades.yml
    modified:   wiki/src/upgrade/v2/Tails/4.5/amd64/stable/upgrades.yml

Untracked files:
  (use "git add <file>..." to include in what will be committed)

    wiki/src/upgrade/v2/Tails/4.0~beta1/amd64/stable/upgrades.yml
    wiki/src/upgrade/v2/Tails/4.0~beta2/amd64/stable/upgrades.yml
    wiki/src/upgrade/v2/Tails/4.0~rc1/amd64/stable/upgrades.yml
    wiki/src/upgrade/v2/Tails/4.2.1/amd64/alpha/upgrades.yml
    wiki/src/upgrade/v2/Tails/4.2.1/amd64/stable/upgrades.yml
    wiki/src/upgrade/v2/Tails/4.2.2/amd64/alpha/upgrades.yml
    wiki/src/upgrade/v2/Tails/4.2.2/amd64/stable/upgrades.yml
    wiki/src/upgrade/v2/Tails/4.5~rc1/amd64/alpha/upgrades.yml
    wiki/src/upgrade/v2/Tails/4.5~rc1/amd64/stable/upgrades.yml

Subtasks

History

#1 Updated by intrigeri 2020-01-10 12:38:27

  • Target version set to Tails_4.2.2

#2 Updated by intrigeri 2020-01-10 12:43:18

  • Assignee changed from intrigeri to CyrilBrulebois

> I’m worried about all those “No IUK could be found for ” while we’ve just went through the troubles of building+verifying them…

Indeed, that’s a buggy output.

I looked at the code and it seems to me that this was the problem I fixed with a9b8ff9f5878cf8e483d5461d6f348a7c2162600 (but again, on master only, and thus not in the copy you forked off stable at the beginning of the release process).

Please retry with that patch applied :)

#3 Updated by CyrilBrulebois 2020-01-10 15:11:07

  • Assignee changed from CyrilBrulebois to intrigeri

Please review commit:e3e357fd5c80288a032f546c79c32a9aec08a967 when you get a chance, to double check what I wrote makes sense, and that everything happening there is expected (as I can’t compare with what has or should have happened for the past release, as they were differences in parameters — IUK_SOURCE_VERSIONS notably — plus the previous version was “supposed-to-be-the-only-one-special”).

#4 Updated by intrigeri 2020-01-10 17:02:52

  • Assignee changed from intrigeri to CyrilBrulebois

I took a very quick look and it LGTM. I have a doubt about the quotes being needed but that should not be a blocker, I guess.

#5 Updated by CyrilBrulebois 2020-01-10 21:03:30

I’d suppose different versions of the underlying libraries (on your system and mine) might explain that discrepancy between the initial version (you provided) and the updated one (that I’ve just generated)?

#6 Updated by intrigeri 2020-01-11 09:09:07

> I’d suppose different versions of the underlying libraries (on your system and mine) might explain that discrepancy between the initial version (you provided) and the updated one (that I’ve just generated)?

Yep, this rings a bell wrt. Stretch vs. Buster/sid’s libyaml-$something behaving differently in this respect.

#7 Updated by intrigeri 2020-01-14 10:49:59

  • Status changed from Confirmed to Resolved