Bug #12308

Unusable tagged APT snapshots are generated when no package is pulled from the corresponding APT repo

Added by intrigeri 2017-03-08 17:24:32 . Updated 2018-01-19 14:10:15 .

Status:
Resolved
Priority:
Normal
Assignee:
Category:
Infrastructure
Target version:
Tails_3.5
Start date:
2017-03-08
Due date:
% Done:

100%

Feature Branch:
Type of work:
Contributors documentation
Blueprint:

Starter:
Affected tool:
Deliverable for:

Description

i.e. the tagged APT snapshot has no Release file, which breaks the ISO build.

Subtasks

Related issues

Related to Tails - Feature #12309: Re-enable debian-security Stretch APT sources once they have packages we would pull Resolved 2017-03-08
Related to Tails - Feature #12310: Re-enable torproject-obfs4proxy APT sources once they have packages newer than Stretch's ones Rejected 2017-03-08

History

#1 Updated by intrigeri 2017-03-08 17:24:49

I’ll take a look during the 2.12 cycle.

#2 Updated by intrigeri 2017-03-08 17:27:16

  • related to Feature #12309: Re-enable debian-security Stretch APT sources once they have packages we would pull added

#3 Updated by intrigeri 2017-03-08 17:31:16

  • related to Feature #12310: Re-enable torproject-obfs4proxy APT sources once they have packages newer than Stretch's ones added

#4 Updated by intrigeri 2017-04-03 07:57:06

  • Target version deleted (Tails_2.12)

Dropping the target version, as the workaround is pretty easy to implement: don’t enable useless APT sources. With a tiny bit of bad faith, one could even argue that it’s a feature, that helps detecting obsolete APT sources we should drop :]

#5 Updated by Anonymous 2018-01-16 09:42:10

So should we close this ticket then? Or do you want to transform it into a documentation ticket?

#6 Updated by intrigeri 2018-01-16 12:39:20

  • Target version set to Tails_3.5
  • Type of work changed from Code to Contributors documentation

u wrote:
> So should we close this ticket then? Or do you want to transform it into a documentation ticket?

I’ve thought a bit about it. We have 3 main options:

  1. Root cause: have our APT snapshots generation code create Release files and empty Packages files for every dist in the input time-based snapshots. Presumably that’s not too hard to do without breaking more important stuff.
  2. Workaround: if we identified this problem before release time (when we tag the APT snapshots) we would avoid triggering this bug; but it is a hard problem.
  3. Doc: add a known issue to https://tails.boum.org/contribute/APT_repository/tagged_snapshots/ that explains this problem and how to fix it when it happens.

This problem happened exactly once in 1.5 years so I don’t think it’s worth investing time into option (1). I’ll do option (3) and call it good enough.

#7 Updated by intrigeri 2018-01-16 13:20:52

  • Status changed from Confirmed to In Progress

Applied in changeset commit:f4df5ae15bd7b20047c0437d8ee9b1d8b2c3c460.

#8 Updated by intrigeri 2018-01-16 13:21:20

  • Assignee changed from intrigeri to anonym
  • % Done changed from 0 to 50
  • QA Check set to Ready for QA

#9 Updated by anonym 2018-01-19 14:10:15

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

LGTM; as long as I find this text, I think it would save me if this problem occurred while building a release in the future.