Feature #6296

Configure reprepro to pull from foreign APT repositories

Added by intrigeri about 12 years ago. Updated about 9 years ago.

Status:
Resolved
Priority:
Normal
Assignee:
Category:
Infrastructure
Target version:
Tails_2.4
Start date:
Due date:
% Done:

100%

Feature Branch:
Type of work:
Sysadmin
Blueprint:

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

Starter:
Affected tool:
Deliverable for:

Description

IOW: update reprepro configuration to allow pulling from the various foreign APT repositories we’re using.

Subtasks

History

#1 Updated by intrigeri about 12 years ago

  • Subject changed from Pull foreign APT repositories into reprepro to Configure reprepro to pull from foreign APT repositories

#2 Updated by intrigeri about 12 years ago

  • Due date deleted (2013-09-27)
  • Start date deleted (2013-09-27)

#3 Updated by intrigeri about 11 years ago

  • Category set to Infrastructure

#4 Updated by BitingBird about 11 years ago

  • Target version set to Sustainability_M1

Setting the same milestone as the parent ticket

#5 Updated by intrigeri about 10 years ago

  • Assignee set to intrigeri
  • Target version changed from Sustainability_M1 to Tails_2.2
  • Parent task changed from Feature #5926 to Feature #9489

#6 Updated by intrigeri about 10 years ago

  • blocked by deleted (Feature #6299: Regularly pull packages from foreign APT repositories)

#7 Updated by intrigeri about 9 years ago

  • blocks deleted (Feature #6295: Evaluate consequences of importing large amounts of packages into reprepro)

#8 Updated by intrigeri about 9 years ago

  • blocked by Feature #6303: Adapt our infrastructure to be able to handle tons of packages added

#9 Updated by intrigeri about 9 years ago

  • Status changed from Confirmed to In Progress
  • % Done changed from 0 to 50
  • Blueprint set to https://tails.boum.org/blueprint/freezable_APT_repository/
  • Starter deleted (Yes)

This is essentially done in https://git-tails.immerda.ch/puppet-tails/tree/manifests/reprepro/snapshots, and a PoC deployment lives on misc.lizard, but it can’t be fully deployed yet as we lack disk space (Feature #6303) and garbage collection mechanisms (see the todo list on the blueprint).

#10 Updated by intrigeri about 9 years ago

We now have the disk space, only garbage collection mechanisms are missing.

#11 Updated by intrigeri about 9 years ago

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

#12 Updated by intrigeri about 9 years ago

  • blocks deleted (Feature #6303: Adapt our infrastructure to be able to handle tons of packages)

#13 Updated by intrigeri about 9 years ago

This was deployed on the production VM and is working fine. GC mechanisms are WIP and should be done by April 3 if no big unexpected problem comes up.

#14 Updated by intrigeri about 9 years ago

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

#15 Updated by intrigeri about 9 years ago

  • Status changed from In Progress to Resolved
  • Assignee deleted (intrigeri)
  • % Done changed from 50 to 100

This was completed in April. The last bits (GC mechanism) are tracked on Feature #6299.