Bug #13413

torproject time-based snapshots for stretch pull from buster

Added by anonym 2017-07-04 10:46:27 . Updated 2017-07-05 05:48:44 .

Status:
Resolved
Priority:
Normal
Assignee:
Category:
Infrastructure
Target version:
Tails_3.1
Start date:
2017-07-04
Due date:
% Done:

100%

Feature Branch:
Type of work:
Sysadmin
Blueprint:

Starter:
Affected tool:
Deliverable for:

Description

While working on Bug #13253 I first tried to be efficient by just bumping the torprojet snapshot to pull the new Tor 0.3.0.9. Specifically we expect to get 0.3.0.9-1~d90.stretch+1 but we get 0.3.0.9-1~d99.buster+1 (also affects devel.

Our APT pinnings look good; actually it seems the time-based snapshot is wrong, cause the 2017070402 torproject snapshot for stretch has version 0.3.0.9-1~d99.buster+1, which seems wrong.

Starting with an elevated priority since if this affects e.g. the debian snapshots this probably could be serious.

Subtasks

Related issues

Blocks Tails - Feature #13233: Core work 2017Q3: Sysadmin (Maintain our already existing services) Resolved 2017-06-29
Blocks Tails - Bug #13416: Restore APT pinning of deb.tp.o Resolved 2017-07-04

History

#1 Updated by intrigeri 2017-07-04 11:19:03

  • blocks Feature #13233: Core work 2017Q3: Sysadmin (Maintain our already existing services) added

#2 Updated by anonym 2017-07-04 11:47:21

  • blocks Bug #13416: Restore APT pinning of deb.tp.o added

#3 Updated by intrigeri 2017-07-04 11:55:53

  • Subject changed from time-based snapshots for stretch can contain versions from buster to torproject time-based snapshots for stretch pull from buster
  • Status changed from Confirmed to In Progress
  • % Done changed from 0 to 10
  • Type of work changed from Research to Sysadmin

Hopefully fixed with https://git-tails.immerda.ch/puppet-tails/commit/?id=bc21029ac192289b28284a76bc1fa73264c73391, we’ll see (next update runs at 17:41 CEST).

#4 Updated by intrigeri 2017-07-04 11:57:20

  • Priority changed from Elevated to Normal
  • Target version set to Tails_3.1

anonym wrote:
> Starting with an elevated priority since if this affects e.g. the debian snapshots this probably could be serious.

I’ve double checked and it doesn’t affect any other archive we take snapshot from.

#5 Updated by intrigeri 2017-07-05 05:48:44

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