Project

General

Profile

Feature #6371

Migrate to Torbutton 1.6

Added by intrigeri about 6 years ago. Updated almost 6 years ago.

Status:
Resolved
Priority:
High
Assignee:
-
Category:
-
Target version:
-
Start date:
10/16/2013
Due date:
% Done:

100%

Feature Branch:
feature/ff24
Type of work:
Code
Blueprint:
Starter:
No
Affected tool:
Browser

Description

Torbutton 1.5.x will probably be EOL as soon as TBB 3.0 is stable (which is blocked on just a couple bugs), so we have to migrate ASAP. The branding additions in 1.6.x may conflict with ours.

Mike Perry writes:

The main things I'd be worried
about if I were you is dealing with Tor Launcher and 1.6.x. Leaving Tor
Launcher out but Torbutton 1.6.x in might cause some problems. You can
also try including Tor Launcher in with extensions.torlauncher.start_tor
set to false, but it still may complain if you don't set the
TOR_CONTROL_PORT and TOR_CONTROL_PASSWD env vars anyway.

... so this is related to #5343.


Related issues

Related to Tails - Feature #5343: Tor Launcher Resolved
Related to Tails - Feature #6370: Migrate to Iceweasel 24 Resolved 10/16/2013

History

#1 Updated by intrigeri about 6 years ago

  • Status changed from Confirmed to In Progress
  • QA Check set to Ready for QA
  • Feature Branch set to feature/ff24

Done in feature/ff24, ready for QA (will be reviewed as part of this branch).

#2 Updated by intrigeri about 6 years ago

  • Assignee set to alant

#3 Updated by alant about 6 years ago

  • Assignee changed from alant to intrigeri
  • % Done changed from 0 to 100
  • QA Check changed from Ready for QA to Pass

#4 Updated by intrigeri about 6 years ago

  • Status changed from In Progress to 11
  • Assignee deleted (intrigeri)

I'll assume Alan simply forgot to mark this ticket as "Fix committed".

#5 Updated by intrigeri almost 6 years ago

  • Status changed from 11 to Resolved

Fixed in 0.22.

Also available in: Atom PDF