Feature #11351

Upgrade to Tor 0.2.8

Added by intrigeri 2016-04-15 04:39:18 . Updated 2016-09-20 16:47:31 .

Status:
Resolved
Priority:
Normal
Assignee:
Category:
Target version:
Tails_2.6
Start date:
2016-03-26
Due date:
% Done:

100%

Feature Branch:
feature/11351-tor-0.2.8
Type of work:
Code
Blueprint:

Starter:
Affected tool:
Deliverable for:

Description

Subtasks

Bug #11285: Check if we need to disable UseDefaultFallbackDirs in Tor 0.2.8+ Resolved

100
Feature #11352: Update time syncing design doc wrt. Fallback Directory Mirrors Resolved

100

Related issues

Blocked by Tails - Feature #9521: Use the chutney Tor network simulator in our test suite Resolved 2016-04-15

History

#1 Updated by anonym 2016-05-08 03:37:27

  • blocked by Feature #9521: Use the chutney Tor network simulator in our test suite added

#2 Updated by anonym 2016-05-08 03:38:19

See Bug #11285#note-6 for why we’re blocked by Feature #9521.

#3 Updated by intrigeri 2016-06-09 10:43:07

Added Tor project’s tor-experimental-0.2.8.x-jessie APT suite to our APT snapshots setup.

#4 Updated by intrigeri 2016-06-10 03:41:10

  • Status changed from Confirmed to In Progress
  • Feature Branch set to feature/11351-tor-0.2.8

#5 Updated by intrigeri 2016-06-10 13:48:52

Status: running the full test suite on it. Then I’ll need to tackle the remaining subtask, and wait for a first suitable Tor 0.2.8 release (the first beta?) to be out.

#6 Updated by intrigeri 2016-07-15 05:49:00

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

I’ve seen all test suite scenarios pass, and the branch now installs 0.2.8.5-rc-1~d80.jessie+1 => if you’re happy enough with it, I suggest we merge into devel ASAP so it gets lots of exposure (e.g. via Jenkins testing all other branches based on devel). What do you think?

#7 Updated by intrigeri 2016-08-01 07:36:41

I’d like to ease reviewing for the 2.6 RM, and to get automated tests running about the combination of all these changes ASAP in the 2.6 dev cycle. So, I’ve merged this work, along with the other major branches I’m proposing for 2.6, into the feature/from-intrigeri-for-2.6 integration branch (Jenkins builds and tests.

#8 Updated by bertagaz 2016-08-06 14:33:33

  • Assignee changed from anonym to bertagaz

Seems like Tor 2.8 is now out since beginning of August. This release breaks the devel (and based branched) build, so this need to be merged ASAP. I’m giving a try to this branch with this new Tor release (+ Bug #11619 which also breaks the build).

#9 Updated by bertagaz 2016-08-07 04:18:53

bertagaz wrote:
> Seems like Tor 2.8 is now out since beginning of August. This release breaks the devel (and based branched) build, so this need to be merged ASAP. I’m giving a try to this branch with this new Tor release (+ Bug #11619 which also breaks the build).

Builds works again with this branch (and my last revert commits) + Bug #11619. Test suite scenarios that depend on Tor work fine too and code looks good to me. I’ve pushed bugfix/11351-11619-tor-2.8-no-torbirdy-patches to give some exposure in Jenkins. Let see how it goes so that we can fix builds based on devel ASAP.

#10 Updated by bertagaz 2016-08-07 09:47:13

  • Status changed from In Progress to Fix committed
  • Assignee deleted (bertagaz)
  • QA Check changed from Ready for QA to Pass

Merged the branch into devel!

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

  • Status changed from Fix committed to Resolved