Feature #6371

Migrate to Torbutton 1.6

Added by intrigeri 2013-10-16 17:44:57 . Updated 2013-12-11 08:15:47 .

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

100%

Feature Branch:
feature/ff24
Type of work:
Code
Blueprint:

Starter:
0
Affected tool:
Browser
Deliverable for:

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 Feature #5343.

Subtasks

Related issues

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

History

#1 Updated by intrigeri 2013-10-27 02:43:20

  • 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 2013-11-16 08:25:25

  • Assignee set to alant

#3 Updated by alant 2013-11-25 03:58:54

  • 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 2013-11-25 04:42:58

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

I’ll assume Alan simply forgot to mark this ticket as “Fix committed”.

#5 Updated by intrigeri 2013-12-11 08:15:47

  • Status changed from Fix committed to Resolved

Fixed in 0.22.