Upgrade to Stretch 9.8 in Tails 3.13
It's scheduled for Saturday, February 16th, 2019: https://release.debian.org/proposed-updates/stable.html
- Status changed from Confirmed to In Progress
- % Done changed from 0 to 10
I've quickly reviewed the list of "processed" (= accepted) packages on https://release.debian.org/proposed-updates/stable.html and tl;dr: the cups and glibc security updates (that got no DSA) would be nice to have.
- % Done changed from 10 to 20
I've compared the
.packages file between 3.12.1 and bugfix/16469-linux-4.19.0-3-devel+force-all-tests at 8a9e266119c17531670e5f66d3a25d7134f4d7a5 (i.e. devel, that picked up Stretch 9.8 already, plus the kernel update that it needs to build) and I could spot nothing particularly scary or unexpected. Will run the full test suite on it locally as Jenkins is broken since the reboot yesterday.
- Subject changed from Consider upgrading to Stretch 9.8 in Tails 3.x to Upgrade to Stretch 9.8 in Tails 3.13
- Type of work changed from Research to Code
Will run the full test suite on it locally as Jenkins is broken since the reboot yesterday.
A few fragile tests failed plus a couple temporary network issues. Seems OK, will prepare a branch based on stable.
- Assignee changed from intrigeri to anonym
- % Done changed from 20 to 50
- QA Check set to Ready for QA
Full test suite passed locally except a few fragile tests: the MAC spoofing failure notifications (never seen them work reliably recently, #16420 and "Using Totem ǂ Watching a WebM video over HTTPS" which often fails these days).
@anonym please review and merge into stable. The branch covers this ticket and #16458.
- Assignee deleted (
- QA Check changed from Ready for QA to Pass
Looks good! I've built stable with this branch merged, and then devel witht that stable merged, and we are indeed not FTBFS anymore! I mostly rely on your testing, though, as I only made sure the builds booted in VMs.