Upgrade to Linux 4.17
linux-image-amd64 in sid now depends on
linux-image-4.17.0-1-amd64. Sooner or later 4.16 will be removed from sid and it won't have security support in Debian anymore, so if we don't upgrade to 4.17 in Tails 3.9, we'll probably have to do that in one of the following bugfix releases, which feels a bit scary.
Upgrade Linux to 4.17 and aufs4 to its current aufs4.17 branch (refs: #15763)
Merge commit '58c096b39962d6eac7b52f5be3aa2887efc947a6' into devel (refs: #15763).
#3 Updated by intrigeri over 1 year ago
- Assignee changed from intrigeri to segfault
- % Done changed from 10 to 50
- Estimated time set to 0.50 h
- QA Check set to Ready for QA
I've seen all automated test suite scenarios pass. 0.5 hour should be enough for a quick code review and booting the ISO on 1 bare metal machine. If you want to, and can, test on more hardware than this, feel free to do so up to 1h (total).
#5 Updated by intrigeri over 1 year ago
- % Done changed from 100 to 90
- QA Check changed from Pass to Dev Needed
Thanks. I've merged the state you've reviewed into devel.
Unfortunately (not really but well) a new src:linux was uploaded with an ABI bump and thus the package name changed => pushed another commit to pick it up. Note that if that package had been updated in Debian with no ABI bump between your review and the freeze, we would have silently & blindly taken this upgrade. So I won't request another review and will only test this on my local hardware + run the full automated test suite before merging.
#6 Updated by intrigeri over 1 year ago
So I won't request another review and will only test this on my local hardware + run the full automated test suite before merging.
Full test suite results look good: all green on my local Jenkins except one scenario that always fails here but passes on lizard, and each individual scenario passed at least once accross the 2 full runs on lizard (each of these runs having 1-3 failures, which is pretty good).