Bug #16120

devel branch FTBFS since Enigmail 2:2.0.8-5~deb9u1 reached Stretch

Added by intrigeri 2018-11-12 12:43:28 . Updated 2019-01-30 11:49:48 .

Status:
Resolved
Priority:
High
Assignee:
Category:
Target version:
Tails_3.12
Start date:
2018-11-12
Due date:
% Done:

100%

Feature Branch:
bugfix/16120-delete-obsolete-enigmail-patch
Type of work:
Code
Blueprint:

Starter:
Affected tool:
Email Client
Deliverable for:

Description

Since the Stretch 9.6 point release:

07:19:54 patching file usr/share/xul-ext/enigmail/install.rdf
07:19:54 Reversed (or previously applied) patch detected!  Assume -R? [n] 
07:19:54 Apply anyway? [n] 
07:19:54 Skipping patch.
07:19:54 1 out of 1 hunk ignored -- saving rejects to file usr/share/xul-ext/enigmail/install.rdf.rej

Subtasks

Related issues

Related to Tails - Feature #15657: Check which version of Enigmail we should ship Resolved 2018-06-15
Blocks Tails - Feature #15506: Core work 2018Q4: Foundations Team Resolved 2018-04-08

History

#1 Updated by intrigeri 2018-11-12 12:44:25

Dear segfault, presumably we can now delete the corresponding patch. Assuming you’ll be the first one to be hit by this problem for practical matters (Feature #15292), can you take it?

#2 Updated by intrigeri 2018-11-12 12:44:38

#3 Updated by intrigeri 2018-11-12 12:45:21

  • related to Feature #15657: Check which version of Enigmail we should ship added

#4 Updated by segfault 2018-11-12 21:05:47

  • Status changed from Confirmed to In Progress

Applied in changeset commit:tails|58034ed52c4e7616dbb222fe342601589bf27f68.

#5 Updated by segfault 2018-11-13 10:51:03

  • Assignee changed from segfault to intrigeri
  • QA Check set to Ready for QA
  • Feature Branch set to bugfix/16120-delete-obsolete-enigmail-patch

#6 Updated by intrigeri 2018-11-15 18:19:26

  • Status changed from In Progress to Fix committed
  • % Done changed from 0 to 100

Applied in changeset commit:tails|5225742f02f43d2207ed1c206e09bb5f8dc22559.

#7 Updated by intrigeri 2018-11-15 18:20:44

  • Assignee deleted (intrigeri)
  • QA Check changed from Ready for QA to Pass

#8 Updated by segfault 2018-11-27 11:36:53

  • Status changed from Fix committed to In Progress

Applied in changeset commit:tails|56385947e6fb20ae58f8650a2a334c3f33bda613.

#9 Updated by intrigeri 2018-11-27 12:27:46

  • Status changed from In Progress to Fix committed

#10 Updated by anonym 2019-01-30 11:49:48

  • Status changed from Fix committed to Resolved