Bug #15763

Upgrade to Linux 4.17

Added by intrigeri 2018-08-04 00:51:06 . Updated 2018-10-03 13:55:28 .

Status:
Resolved
Priority:
Elevated
Assignee:
Category:
Target version:
Tails_3.9
Start date:
2018-08-04
Due date:
% Done:

100%

Feature Branch:
feature/15763-linux-4.17
Type of work:
Code
Blueprint:

Starter:
Affected tool:
Deliverable for:

Description

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.

Subtasks

Related issues

Blocks Tails - Feature #15334: Core work 2018Q3: Foundations Team Resolved 2018-02-20

History

#1 Updated by intrigeri 2018-08-04 00:53:38

  • Feature Branch set to feature/15763-linux-4.17

#2 Updated by intrigeri 2018-08-04 13:37:44

  • Status changed from Confirmed to In Progress
  • % Done changed from 0 to 10

#3 Updated by intrigeri 2018-08-07 12:41:57

  • Assignee changed from intrigeri to segfault
  • % Done changed from 10 to 50
  • Estimated time set to 0 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).

#4 Updated by segfault 2018-08-14 16:41:51

  • Assignee changed from segfault to intrigeri
  • % Done changed from 50 to 100
  • QA Check changed from Ready for QA to Pass

Works on my hardware (I could only test one machine)

#5 Updated by intrigeri 2018-08-14 17:53:01

  • % 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 2018-08-15 05:22:48

intrigeri wrote:
> 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).

#7 Updated by intrigeri 2018-08-15 08:31:08

  • Status changed from In Progress to Fix committed
  • Assignee deleted (intrigeri)
  • % Done changed from 90 to 100
  • QA Check changed from Dev Needed to Pass

Works on 2 laptops, merged.

#8 Updated by intrigeri 2018-08-16 09:14:32

  • Status changed from Fix committed to In Progress

Applied in changeset commit:d9033ef9d811f66222d2d8249e172f0a24dc5578.

#9 Updated by intrigeri 2018-08-16 09:14:34

  • Status changed from In Progress to Fix committed

Applied in changeset commit:0506ce79df32c89d72a66aa1527d097448ae6548.

#10 Updated by intrigeri 2018-09-05 16:16:46

  • Status changed from Fix committed to Resolved

#11 Updated by segfault 2018-10-03 10:04:23

#12 Updated by segfault 2018-10-03 10:04:56

I assume this qualifies as FT work

#13 Updated by intrigeri 2018-10-03 13:55:28

> I assume this qualifies as FT work

Absolutely :)