Project

General

Profile

Feature #10749

Feature #5926: Freezable APT repository

Feature #9489: Implement packages importing and freezing

Create partial APT snapshot from a build manifest and a set of time-based snapshots

Added by intrigeri over 3 years ago. Updated about 3 years ago.

Status:
Resolved
Priority:
Normal
Assignee:
-
Category:
Infrastructure
Target version:
Tails_2.4
Start date:
12/13/2015
Due date:
% Done:

100%

Feature Branch:
Type of work:
Code
Blueprint:

https://tails.boum.org/blueprint/freezable_APT_repository/

Starter:
Affected tool:

Description

This is mainly about the tails-prepare-tagged-apt-snapshot-import script (puppet-tails repo) and the glue + Puppet bits that will make it usable.

Related issues

Blocks Tails - Feature #6310: Publish source Debian packages used by Tails ISO images Resolved 09/26/2013

History

#1 Updated by intrigeri over 3 years ago

  • Blocked by Feature #10748: Generate a manifest of packages used at build time added

#2 Updated by intrigeri over 3 years ago

  • Description updated (diff)
  • % Done changed from 20 to 10
  • Feature Branch set to puppet-tails:kibi/master

Note that there are two implementations (kibi/pu/master-v1, kibi/master). The latter is slower but uses Dpkg::Control instead of a home-made parser.

#3 Updated by intrigeri over 3 years ago

A potential lacking feature in the current code is being discussed over email: "Tails#10748, Tails#10749: architectures". But this shouldn't block me from testing/reviewing the rest :)

#4 Updated by intrigeri over 3 years ago

  • Target version changed from Tails_2.2 to Tails_2.3

#5 Updated by intrigeri over 3 years ago

intrigeri wrote:

Note that there are two implementations (kibi/pu/master-v1, kibi/master). The latter is slower but uses Dpkg::Control instead of a home-made parser.

I've merged the version that uses Dpkg::Control: even if it's slower, it's cheaper to maintain and we only run that ~once per release.

However, on this ticket we need to handle the problem raised in the "Tails#10748: build manifest vs. multiple origins" email thread.

#6 Updated by intrigeri over 3 years ago

  • Assignee changed from intrigeri to CyrilBrulebois

#7 Updated by intrigeri over 3 years ago

intrigeri wrote:

However, on this ticket we need to handle the problem raised in the "Tails#10748: build manifest vs. multiple origins" email thread.

Done. More work is needed, see the blueprint for details.

#8 Updated by intrigeri over 3 years ago

  • Assignee changed from CyrilBrulebois to intrigeri
  • % Done changed from 10 to 30
  • QA Check set to Ready for QA
  • Feature Branch deleted (puppet-tails:kibi/master)

#9 Updated by intrigeri over 3 years ago

  • Blocked by deleted (Feature #10748: Generate a manifest of packages used at build time)

#10 Updated by intrigeri over 3 years ago

  • QA Check deleted (Ready for QA)

The script was improved this month and is now working fine; remaining integration bits are listed on the blueprint.

#11 Updated by intrigeri over 3 years ago

  • Blocks Feature #6310: Publish source Debian packages used by Tails ISO images added

#12 Updated by intrigeri about 3 years ago

  • Target version changed from Tails_2.3 to Tails_2.4

#13 Updated by intrigeri about 3 years ago

  • Blocked by Feature #10748: Generate a manifest of packages used at build time added

#14 Updated by intrigeri about 3 years ago

  • % Done changed from 30 to 40

Integration was done up to the point when a build from tagged snapshots succeeded. Remaining bits are listed on the blueprint.

#15 Updated by intrigeri about 3 years ago

  • % Done changed from 40 to 50

I've confirmed that a build from a given tagged snapshot has the same packages and build manifest as the build (from time-based snapshots) whose build manifest was used to generate that tagged snapshot, so we're good. Only a couple cleanup / follow-up tiny tasks are left, so we're basically done here, until we're ready to have the entire parent task reviewed'n'merged.

#16 Updated by intrigeri about 3 years ago

  • Assignee changed from intrigeri to bertagaz
  • QA Check set to Ready for QA

Regarding the Puppet review, it's the same as #6299, really: start in manifests/reprepro/snapshots/ in puppet-tails, and follow the white rabbit (classes, templates, files).

#17 Updated by intrigeri about 3 years ago

  • Assignee changed from bertagaz to intrigeri
  • % Done changed from 50 to 60
  • QA Check changed from Ready for QA to Dev Needed

The review bertagaz posted on #6299#note-15 covers these bits too.

#18 Updated by intrigeri about 3 years ago

  • Assignee changed from intrigeri to bertagaz
  • % Done changed from 60 to 70
  • QA Check changed from Dev Needed to Ready for QA

(Same as #6299.)

#19 Updated by intrigeri about 3 years ago

  • Blocked by deleted (Feature #10748: Generate a manifest of packages used at build time)

#20 Updated by intrigeri about 3 years ago

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

Same as #6299.

Also available in: Atom PDF