Tails

#1 Updated by intrigeri 2017-06-22 14:25:23

• Assignee set to bertagaz
• Target version set to Tails_3.1

> I.e. the last stable build (#1589) failed with:

This has been fixed apparently. bertagaz, what was the root cause, and how likely is it that this problem hits us again in the future?

#2 Updated by intrigeri 2017-06-24 17:49:29

• Status changed from Confirmed to In Progress
• % Done changed from 0 to 10

This happened again a lot today.

This problem happens when the debian archive fails to synchronize, but that’s anecdoctical (although bertagaz should fix it anyway as part of his sysadmin shift: this has happened once a day this week).

The real problem is that we use the latest serial of the debian-security archive for jessie-updates, which lives in the debian archive:

sed -i -e "s/${stable_serial}/${security_serial}/g" /etc/apt/sources.list.d/jessie-updates.list

I think this code should modify jessie-security.list, rather than jessie-updates.list: the “Always set the latest serial for debian-security” comment suggests that the code doesn’t do what it should.

Keeping this assigned to bertagaz, since this bug was introduced in commit:5dd2cad7c6a7867af3d4e652bfafa0b8787f7e20, that it authored.

#3 Updated by intrigeri 2017-06-25 09:59:37

• Assignee changed from bertagaz to intrigeri

Due to this problem I simply can’t build any ISO locally, which blocks my Foundation Team work. There’s been no update from bertagaz here yet, so I’m taking this over.

#4 Updated by intrigeri 2017-06-25 10:10:12

• related to Bug #13134: The Debian mirror used as upstream for our time-based snapshots is buggy added

#5 Updated by intrigeri 2017-06-25 10:10:37

• related to Bug #12725: Sort out the apt-snapshots-disk partition situation on apt.lizard added

#6 Updated by intrigeri 2017-06-25 10:11:44

• Feature Branch set to bugfix/12829-buggy-APT-sources-in-buildbox

#7 Updated by intrigeri 2017-06-25 10:13:37

• Subject changed from FTBFS due to problems with the 20170621* APT snapshots to FTBFS due to buggy APT sources set in Vagrant build box by the provision script

#8 Updated by intrigeri 2017-06-25 11:28:26

• % Done changed from 10 to 20
• QA Check set to Ready for QA

Pushed straight to stable + devel, let’s see how it goes.

#9 Updated by intrigeri 2017-06-25 12:38:48

• Assignee changed from intrigeri to bertagaz
• % Done changed from 20 to 50

The sources used in https://jenkins.tails.boum.org/view/RM/job/build_Tails_ISO_devel/2433/consoleFull look OK: frozen sources are used when creating the basebox, and up-to-date sources are used for debian-security (and nothing else) when running the provisioning script. Same for https://jenkins.tails.boum.org/view/Tails_ISO_builds/job/build_Tails_ISO_stable/1595/console, so I think the problem is fixed, and I can resume my Foundations Team work :)

Please double check that both my changes and the outcome make sense to you.

#10 Updated by bertagaz 2017-06-29 14:51:33

• Status changed from In Progress to Resolved
• Assignee deleted (bertagaz)
• % Done changed from 50 to 100
• QA Check changed from Ready for QA to Pass

intrigeri wrote:
> The sources used in https://jenkins.tails.boum.org/view/RM/job/build_Tails_ISO_devel/2433/consoleFull look OK: frozen sources are used when creating the basebox, and up-to-date sources are used for debian-security (and nothing else) when running the provisioning script. Same for https://jenkins.tails.boum.org/view/Tails_ISO_builds/job/build_Tails_ISO_stable/1595/console, so I think the problem is fixed, and I can resume my Foundations Team work :)
>
> Please double check that both my changes and the outcome make sense to you.

Looks good! Thanks for the hotfix.

#11 Updated by intrigeri 2017-06-30 06:20:53

• Target version changed from Tails_3.1 to Tails_3.0.1