Bug #11757

Tails 2.6-rc1 ships older Tor version

Added by spriver 2016-09-02 14:19:28 . Updated 2016-09-20 16:47:50 .

Status:
Resolved
Priority:
High
Assignee:
Category:
Build system
Target version:
Start date:
2016-09-02
Due date:
% Done:

100%

Feature Branch:
bugfix/11757-bump-torproject-snapshot
Type of work:
Code
Blueprint:

Starter:
Affected tool:
Deliverable for:

Description

The rc1 comes with Tor version 0.2.8.6-2~d80, deb.torproject.org lists tor_0.2.8.7-1~d80.


Subtasks


History

#1 Updated by anonym 2016-09-02 14:37:26

  • Category set to Build system
  • Assignee changed from anonym to intrigeri
  • QA Check set to Info Needed

If we look at <http://deb.torproject.org/torproject.org/pool/main/t/tor/> we find e.g. tor_0.2.8.7-1_i386.deb from 2016-08-25 07:49, but since I froze the testing branch we have:

./auto/scripts/apt-snapshots-serials cat
debian: 2016090203
debian-security: latest
torproject: 2016081703


So our latest torproject snapshot is very outdated. I’m not really sure how to debug this effectively.

Any ideas, intrigeri or kibi?

#2 Updated by anonym 2016-09-02 14:43:07

BTW, I have verified that only the tor (and tor-geoipdb) package is affected by this; all other packages we installed from deb.torproject.org are up-to-date.

#3 Updated by intrigeri 2016-09-03 01:48:34

  • Status changed from Confirmed to In Progress
  • % Done changed from 0 to 10
  • QA Check deleted (Info Needed)

Fixed the root cause of the problem on the infra side, will build with the latest snapshot and push to testing and devel.

#4 Updated by intrigeri 2016-09-03 01:55:48

  • Assignee changed from intrigeri to anonym
  • Priority changed from Elevated to High
  • % Done changed from 10 to 20
  • QA Check set to Dev Needed

The build of testing + additional changes seems to be broken at this point (“Not building from a tag, but last version in changelog was released”) so I’ll let anonym handle this. My patch was:

commit 9f9bb97f8601fa8c4257f247b75711a812215967
Author: intrigeri <intrigeri@boum.org>
Date:   Sat Sep 3 08:46:50 2016 +0000

    Bump torproject APT snapshot.

    refs: <del><a class='issue tracker-1 status-3 priority-6 priority-default closed child' href='/code/issues/11757' title='Tails 2.6-rc1 ships older Tor version'>Bug #11757</a></del>

diff --git a/config/APT_snapshots.d/torproject/serial b/config/APT_snapshots.d/torproject/serial
index cb91172..970cbde 100644
--- a/config/APT_snapshots.d/torproject/serial
+++ b/config/APT_snapshots.d/torproject/serial
@@ -1 +1 @@
-2016081703
+2016090301

#5 Updated by intrigeri 2016-09-10 04:16:54

  • Assignee changed from anonym to intrigeri

After hopefully fixing the build of testing (by doing some post-RC release process steps that were apparently skipped), I’m back working on this. Will submit a branch later today :)

#6 Updated by intrigeri 2016-09-10 05:27:14

  • % Done changed from 20 to 30
  • Feature Branch set to bugfix/11757-bump-torproject-snapshot

Compared to 2.6~rc1’s .packages:

@@ -82,7 +82,7 @@
 dconf-cli  0.22.0-1
 dconf-gsettings-backend:i386   0.22.0-1
 dconf-service  0.22.0-1
-deb.torproject.org-keyring 2014.08.31+b1
+deb.torproject.org-keyring 2016.08.22
 debconf    1.5.56
 debconf-i18n   1.5.56
 debian-archive-keyring 2014.3
@@ -1741,9 +1741,9 @@
 tcpflow    1.4.4+repack1-3
 telepathy-mission-control-5    1:5.16.3-1
 tk8.6-blt2.5   2.5.3+dfsg-1
-tor    0.2.8.6-2~d80.jessie+1
+tor    0.2.8.7-1~d80.jessie+1
 tor-arm    1.4.5.0-1
-tor-geoipdb    0.2.8.6-2~d80.jessie+1
+tor-geoipdb    0.2.8.7-1~d80.jessie+1
 torsocks   2.1.0-1~bpo8+1
 totem  3.14.0-2
 totem-common   3.14.0-2

Let’s now see how Jenkins feels about it.

#7 Updated by intrigeri 2016-09-12 01:57:28

  • Assignee changed from intrigeri to anonym
  • % Done changed from 30 to 50
  • QA Check changed from Dev Needed to Ready for QA

Looks OK on Jenkins.

#8 Updated by anonym 2016-09-15 05:56:51

  • Assignee changed from anonym to intrigeri
  • QA Check changed from Ready for QA to Info Needed

My build of this branch fails with:

Err http://time-based.snapshots.deb.tails.boum.org obfs4proxy/main amd64 Packages
  404  Not Found
Err http://time-based.snapshots.deb.tails.boum.org obfs4proxy/main i386 Packages
  404  Not Found
Ign http://time-based.snapshots.deb.tails.boum.org obfs4proxy/main Translation-en
Err http://time-based.snapshots.deb.tails.boum.org jessie/main amd64 Packages
  404  Not Found
Err http://time-based.snapshots.deb.tails.boum.org jessie/main i386 Packages
  404  Not Found
Ign http://time-based.snapshots.deb.tails.boum.org jessie/main Translation-en
Err http://time-based.snapshots.deb.tails.boum.org sid/main amd64 Packages
  404  Not Found
Err http://time-based.snapshots.deb.tails.boum.org sid/main i386 Packages
  404  Not Found
Ign http://time-based.snapshots.deb.tails.boum.org sid/main Translation-en
W: Conflicting distribution: http://time-based.snapshots.deb.tails.boum.org jessie/updates InRelease (expected jessie but got jessie/updates)
W: Failed to fetch http://time-based.snapshots.deb.tails.boum.org/torproject/2016090301/dists/obfs4proxy/main/binary-amd64/Packages  404  Not Found

W: Failed to fetch http://time-based.snapshots.deb.tails.boum.org/torproject/2016090301/dists/obfs4proxy/main/binary-i386/Packages  404  Not Found

W: Failed to fetch http://time-based.snapshots.deb.tails.boum.org/torproject/2016090301/dists/jessie/main/binary-amd64/Packages  404  Not Found

W: Failed to fetch http://time-based.snapshots.deb.tails.boum.org/torproject/2016090301/dists/jessie/main/binary-i386/Packages  404  Not Found

W: Failed to fetch http://time-based.snapshots.deb.tails.boum.org/torproject/2016090301/dists/sid/main/binary-amd64/Packages  404  Not Found

W: Failed to fetch http://time-based.snapshots.deb.tails.boum.org/torproject/2016090301/dists/sid/main/binary-i386/Packages  404  Not Found

E: Some index files failed to download. They have been ignored, or old ones used instead.


Unsurprisingly, the 2016090301 snapshot doesn’t exist, because the infra side was fixed after 2016-09-03 01:00. Either that, or it expired, because it’s now >10 days ago. I say: let’s just get the most recent snapshot and use that for Tails 2.6. What do you think?

I am currently building with the 2016091502 snapshot. I’ll report back the results…

#9 Updated by intrigeri 2016-09-15 07:30:20

  • Assignee changed from intrigeri to anonym
  • QA Check changed from Info Needed to Dev Needed

> Unsurprisingly, the 2016090301 snapshot doesn’t exist, because the infra side was fixed after 2016-09-03 01:00. Either that, or it expired, because it’s now >10 days ago.

Yes, it has expired (postponing the expiration date is part of the release process, which explains why this snapshot was not covered).

> I say: let’s just get the most recent snapshot and use that for Tails 2.6. What do you think?

Sure. I’m pretty sure it has the same content anyway :)

#10 Updated by anonym 2016-09-15 09:27:53

  • Status changed from In Progress to Fix committed
  • Assignee deleted (anonym)
  • % Done changed from 50 to 100
  • QA Check changed from Dev Needed to Pass

intrigeri wrote:
> > I say: let’s just get the most recent snapshot and use that for Tails 2.6. What do you think?
>
> Sure.

I’ve pushed your commit modified like so straight into testing because…

> I’m pretty sure it has the same content anyway :)

… my package diff of a build is the same as yours in Bug #11757#note-6, which is the sought after outcome.

#11 Updated by anonym 2016-09-20 16:47:50

  • Status changed from Fix committed to Resolved