Feature #7620
Drop Tor Launcher patch that relabels the finish button
100%
Subtasks
Related issues
Related to Tails - |
Rejected | 2014-05-26 | |
Related to Tails - |
Resolved | 2014-04-15 | |
Blocked by Tails - |
Resolved | 2014-09-22 |
History
#1 Updated by intrigeri 2014-07-19 19:15:38
- related to
Bug #7282: Tor Launcher: Don't relabel finish button when not owning Tor. added
#2 Updated by BitingBird 2015-01-07 16:30:31
- Affected tool set to Tor Launcher
#3 Updated by BitingBird 2015-04-10 16:01:07
Has this been done? If not, could this be done for 1.4? Seems like a tiny change to me, that brings us closer to upstream and is unlikely to make bugs, so…
#4 Updated by intrigeri 2015-04-11 10:01:07
- related to
Feature #7087: Do not bundle Tor Launcher in the main Tails Git repository added
#5 Updated by intrigeri 2015-04-11 10:01:53
- Target version set to Tails_1.4
- Feature Branch set to feature/8925-tor-0.2.6
I think that’ll be fixed at the same time as Feature #7087. anonym, if I got it wrong (sorry) then feel free to revert the metadata changes I’m doing on this ticket.
#6 Updated by anonym 2015-04-29 11:44:15
- Status changed from Confirmed to In Progress
- Assignee deleted (
anonym) - % Done changed from 0 to 50
- QA Check set to Ready for QA
intrigeri wrote:
> I think that’ll be fixed at the same time as Feature #7087. anonym, if I got it wrong (sorry) then feel free to revert the metadata changes I’m doing on this ticket.
Well, I guess it’s a matter of perspective. With Feature #7087 done, we completely drop our bundled Tor Launcher, so you can either see it as we drop it, or that this ticket should be rejected. I guess I continue with your approach.
#7 Updated by anonym 2015-04-29 11:44:37
- blocked by
Feature #7934: Upgrade to Tor 0.2.6.x added
#8 Updated by intrigeri 2015-05-01 10:00:11
- Status changed from In Progress to Fix committed
- % Done changed from 50 to 100
Applied in changeset commit:e88f3b27b295e745eb31af186fc48879bc4a1ca0.
#9 Updated by BitingBird 2015-05-01 10:12:47
- QA Check changed from Ready for QA to Pass
#10 Updated by BitingBird 2015-05-12 18:46:09
- Status changed from Fix committed to Resolved