ISO builds are broken by weird enigmail situation
It seems that our build system is trying to install 2:126.96.36.199-1~deb9u1 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:188.8.131.52-1~deb9u1, http://metadata.ftp-master.debian.org/changelogs/main/e/enigmail/enigmail_184.108.40.206-1~deb9u1_changelog gives me a 404, and rmadison doesn’t know what’s going on either, so I wonder what’s going on.
#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.
#11 Updated by bertagaz 2017-07-31 10:12:38
- Status changed from In Progress to Fix committed
- Assignee deleted (
- % Done changed from 50 to 100
- QA Check changed from Ready for QA to Pass
> 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.