Feature #16687: Upgrade to tor 0.4.x

Feature #16687

Upgrade to tor 0.4.x

Added by intrigeri 2019-05-03 10:38:50 . Updated 2019-07-03 08:03:31 .

Status:

Resolved

Priority:

Normal

Assignee:

Category:

Target version:

Tails_3.14.1

Start date:

Due date:

% Done:

Feature Branch:

feature/16687-tor-0.4.0.x+force-all-tests

Type of work:

Code

Blueprint:

Starter:

Affected tool:

Deliverable for:

Description

Subtasks

Related issues

Blocks Tails - Feature #16209: Core work: Foundations Team	Confirmed
Blocks Tails - Bug #16471: Drop time synchronization hacks that tor 0.3.5 and 0.4.x made obsolete	In Progress	2019-02-17
Blocks Tails - ~~Bug #16790~~: Revert to installing tor from torproject's buster suite	Resolved

History

#1 Updated by intrigeri 2019-05-03 10:38:58

blocks Feature #16209: Core work: Foundations Team added

#2 Updated by hefee 2019-05-21 22:30:05

blocks Bug #16471: Drop time synchronization hacks that tor 0.3.5 and 0.4.x made obsolete added

#3 Updated by intrigeri 2019-05-24 07:05:48

Subject changed from Upgrade to Tor 0.4.x to Upgrade to tor 0.4.x

#4 Updated by intrigeri 2019-05-24 07:07:26

Type of work changed from Code to Wait

Let’s wait for https://deb.torproject.org/torproject.org/dists/stretch/main/binary-amd64/Packages to have 0.4.x. I’m not sure what’s the reason for the delay (we could ask weasel) since 0.4.x was declared stable already.

#5 Updated by intrigeri 2019-06-08 07:25:23

Type of work changed from Wait to Code

intrigeri wrote:
> Let’s wait for https://deb.torproject.org/torproject.org/dists/stretch/main/binary-amd64/Packages to have 0.4.x. I’m not sure what’s the reason for the delay (we could ask weasel) since 0.4.x was declared stable already.

I see 0.4.0.5 is packaged in https://deb.torproject.org/torproject.org/dists/tor-experimental-0.4.0.x-stretch/main/binary-amd64/Packages. I’m pretty sure I’m guessing right that it’s there, and not in their stretch dist, only because tor 0.4.x will only be in Debian experimental until the Buster release. I don’t think we should block on this to upgrade ourselves given 0.4.x is stable from upstream’s PoV and this upgrade is needed for other ongoing work of ours (Bug #16471).

So IMO we should:

create a branch forked off stable that switches to the tor-experimental-0.4.0.x-stretch dist; then work that depends on tor 0.4.x can be based on that new branch
file a ticket to revert this change once 0.4.x is in the stretch dist

#6 Updated by intrigeri 2019-06-08 07:35:22

Assignee set to intrigeri

intrigeri wrote:
> * create a branch forked off stable that switches to the tor-experimental-0.4.0.x-stretch dist; then work that depends on tor 0.4.x can be based on that new branch

I’ll do that so that I can push to Jenkins a branch based on stable that has hefee’s changes from Bug #16471 except the Chutney ones. At this point I’m not committing to do more on this very ticket though.