Bug #13530

ISO builds are broken by weird enigmail situation

Added by intrigeri 2017-07-29 06:55:25 . Updated 2017-08-09 12:38:27 .

Target version:
Start date:
Due date:
% Done:


Feature Branch:
Type of work:

Affected tool:
Email Client
Deliverable for:


It seems that our build system is trying to install 2: from stretch/updates, that depends on Thunderbird 52 while we still ship Thunderbird 45. If that was the only problem, then the obvious solution is to upload 2:1.9.7-2 to our custom APT repo.

But https://tracker.debian.org/pkg/enigmail doesn’t know about 2:, http://metadata.ftp-master.debian.org/changelogs/main/e/enigmail/enigmail_1.9.8.1-1~deb9u1_changelog gives me a 404, and rmadison doesn’t know what’s going on either, so I wonder what’s going on.


Related issues

Related to Tails - Feature #12639: Upgrade Thunderbird to 52.x Resolved 2017-06-05
Blocks Tails - Feature #13234: Core work 2017Q3: Foundations Team Resolved 2017-06-29
Blocks Tails - Feature #11738: Upgrade our ISO builder Vagrant basebox to Stretch Resolved 2016-08-28


#1 Updated by intrigeri 2017-07-29 06:58:57

I’ve received a DSA 3921-1 email that announces this upgrade yesterday night, but https://www.debian.org/security/2017/dsa-3921 is 404 too. So it seems that this update & security advisory are in a weird, half-assed situation. Anyway, let’s not care, just ensure we install the version of enigmail we want for 3.1, and leave it to Feature #12639 to do the next steps.

#2 Updated by intrigeri 2017-07-29 07:03:30

#3 Updated by intrigeri 2017-07-29 07:05:27

#4 Updated by intrigeri 2017-07-29 07:06:47

  • Feature Branch set to bugfix/13530-enigmail-compatible-with-thunderbird-45

#5 Updated by intrigeri 2017-07-29 07:13:42

  • Status changed from Confirmed to In Progress

Applied in changeset commit:158eb4e4213fe2c4eca0afc64997e1162b54d591.

#6 Updated by intrigeri 2017-07-29 08:17:40

  • Assignee changed from intrigeri to bertagaz
  • Priority changed from Elevated to High
  • % Done changed from 0 to 50

I’ve seen an ISO build succeed on that branch, didn’t validate it further given how urgent this is.

#7 Updated by intrigeri 2017-07-29 08:17:53

  • QA Check set to Ready for QA

#8 Updated by intrigeri 2017-07-29 15:09:42

  • blocks Bug #13531: Use ikiwiki 3.20161219+, again added

#9 Updated by intrigeri 2017-07-29 18:32:15

  • blocks Feature #11738: Upgrade our ISO builder Vagrant basebox to Stretch added

#10 Updated by intrigeri 2017-07-29 19:50:11

  • blocked by deleted (Bug #13531: Use ikiwiki 3.20161219+, again)

#11 Updated by bertagaz 2017-07-31 10:12:38

  • Status changed from In Progress to Fix committed
  • Assignee deleted (bertagaz)
  • % Done changed from 50 to 100
  • QA Check changed from Ready for QA to Pass

intrigeri wrote:
> I’ve seen an ISO build succeed on that branch, didn’t validate it further given how urgent this is.

It indeed fix the build, and passes the tests in Jenkins and locally, so it’s now merged in stable and devel.

#12 Updated by bertagaz 2017-08-09 12:38:27

  • Status changed from Fix committed to Resolved