Bug #11078
Fail to build ISO since torbrowser-launcher 0.2.2-3 reached Debian testing
Start date:
2016-02-08
Due date:
% Done:
100%
Description
Another occurence of “our current CI checks for this are not testing the right thing so nobody who was supposed to deal with such problems is aware of it except me, and even I learn about it too late”. I’ll deal with it.
Subtasks
Related issues
Related to Tails - Bug #10582: merge_from_torbrowser-launcher_upstream Jenkins job is not testing what it should | Confirmed | 2015-11-19 |
History
#1 Updated by intrigeri 2016-02-08 12:20:37
- related to Bug #10582: merge_from_torbrowser-launcher_upstream Jenkins job is not testing what it should added
#2 Updated by intrigeri 2016-02-08 12:28:33
- Status changed from Confirmed to In Progress
- % Done changed from 0 to 10
- Feature Branch set to bugfix/11078-refresh-Tor-Browser-AppArmor-profile
#3 Updated by intrigeri 2016-02-08 13:00:13
- Assignee deleted (
intrigeri) - % Done changed from 10 to 50
- QA Check set to Ready for QA
At least the build passes the step that was failing.
#4 Updated by intrigeri 2016-02-08 13:06:38
- Assignee set to anonym
#5 Updated by intrigeri 2016-02-08 14:54:54
- Status changed from In Progress to Resolved
- % Done changed from 50 to 100
Applied in changeset commit:488dec2acd859009a76a029e1cb2a3382e7e63f3.
#6 Updated by intrigeri 2016-02-08 14:56:54
- Status changed from Resolved to In Progress
- % Done changed from 100 to 90
Merged into stable and devel to stop the avalanche of build failure notifications, but please review.
#7 Updated by anonym 2016-02-08 15:44:48
- Status changed from In Progress to Fix committed
- Assignee deleted (
anonym) - % Done changed from 90 to 100
- QA Check changed from Ready for QA to Pass
intrigeri wrote:
> Applied in changeset commit:488dec2acd859009a76a029e1cb2a3382e7e63f3.
I tested this at the same time, and only learned that you had merged the branch when my push was rejected. :)
#8 Updated by intrigeri 2016-02-08 22:40:14
Sorry for creating this race condition!
#9 Updated by bertagaz 2016-02-13 14:19:51
- Status changed from Fix committed to Resolved
#10 Updated by intrigeri 2016-02-13 15:37:47
- Target version changed from Tails_2.2 to Tails_2.0.1