Bug #16077
devel branch FTBFS because of newer torbirdy in stretch-backports
Start date:
2018-10-27
Due date:
% Done:
100%
Description
The devel
branch built fine until 2018-10-25, but started FTBFSing on 2018-10-26, due to a failure to apply the torbirdy install.rdf
patch:
P: Applying patch config/chroot_local-patches/torbirdy-60.2-compat.diff...
patching file usr/share/xul-ext/torbirdy/install.rdf
Reversed (or previously applied) patch detected! Assume -R? [n]
Apply anyway? [n]
Skipping patch.
1 out of 1 hunk ignored -- saving rejects to file usr/share/xul-ext/torbirdy/install.rdf.rej
This is due to the upload of torbirdy 0.2.6-1~bpo9+1 to stretch-backports, replacing 0.2.5-1~bpo9+1.
Dropping the patch should be sufficient to get everything back in order.
Subtasks
Related issues
Blocks Tails - |
Resolved | 2018-04-08 |
History
#1 Updated by intrigeri 2018-10-27 08:30:14
- blocks
Feature #15506: Core work 2018Q4: Foundations Team added
#2 Updated by intrigeri 2018-10-27 08:31:11
- Category set to Build system
- Status changed from New to Confirmed
- Assignee set to segfault
- Priority changed from Normal to High
- Target version set to Tails_3.11
- Affected tool set to Email Client
segfault, do you want to take this one? I expect you’ll be the first one affected when working on the USB image project.
#3 Updated by segfault 2018-10-30 16:17:04
intrigeri wrote:
> segfault, do you want to take this one?
sure
#4 Updated by segfault 2018-10-30 16:28:09
- % Done changed from 0 to 10
- Feature Branch set to bugfix/devel-FTBFS-because-of-torbirdy
Pushed a commit which removes the obsolete patch to the feature branch. Now waiting to see whether Jenkins can build the branch.
#5 Updated by intrigeri 2018-11-01 11:16:24
- Status changed from Confirmed to Fix committed
- % Done changed from 10 to 100
Applied in changeset commit:tails|79a45981e1efcdc7f8b0bbd5ce0e20bf6c33a370.
#6 Updated by intrigeri 2018-11-01 11:16:59
- Assignee deleted (
segfault) - Target version changed from Tails_3.11 to Tails_3.12
Thanks!
#7 Updated by anonym 2019-01-30 11:49:36
- Status changed from Fix committed to Resolved