Bug #15958
devel branch FTBFS since torbrowser-launcher 0.2.9-5 is in sid
Start date:
2018-09-18
Due date:
% Done:
100%
Description
Subtasks
Related issues
Blocks Tails - |
Resolved | 2018-02-20 |
History
#1 Updated by intrigeri 2018-09-18 08:17:44
- blocks
Feature #15334: Core work 2018Q3: Foundations Team added
#2 Updated by intrigeri 2018-09-19 08:44:50
- Status changed from Confirmed to In Progress
- % Done changed from 0 to 10
- Feature Branch set to torbrowser-launcher:bugfix/15958-torbrowser-launcher-0.2.9-5, bugfix/15958-torbrowser-launcher-0.2.9-5+force-all-tests
#3 Updated by intrigeri 2018-09-19 17:02:50
- Assignee changed from intrigeri to segfault
- % Done changed from 10 to 50
- QA Check set to Ready for QA
Only unrelated failures during a full test suite run.
#4 Updated by segfault 2018-09-22 09:12:40
- Assignee changed from segfault to intrigeri
- QA Check changed from Ready for QA to Pass
LGTM, but I wonder why the branch is based on devel. I expected it to be based on stable, because its a bug fix.
#5 Updated by intrigeri 2018-09-25 06:31:32
- Status changed from In Progress to Fix committed
- Assignee deleted (
intrigeri) - % Done changed from 50 to 100
segfault wrote:
> LGTM,
Thank you. Merged!
> but I wonder why the branch is based on devel. I expected it to be based on stable, because its a bug fix.
The bug only applies to devel: stable has frozen APT repos that do not include this torbrowser-launcher upgrade :)
#6 Updated by segfault 2018-09-25 07:25:56
intrigeri wrote:
> The bug only applies to devel: stable has frozen APT repos that do not include this torbrowser-launcher upgrade :)
Oh, right facepalm
#7 Updated by intrigeri 2018-10-01 13:29:43
- Target version changed from Tails_3.10.1 to Tails_3.9.1
#8 Updated by anonym 2018-10-04 10:42:47
- Status changed from Fix committed to Resolved