Bug #15622

Upgrade to Linux 4.16+ in Tails 3.9

Added by intrigeri 2018-05-28 07:23:54 . Updated 2018-09-05 16:08:04 .

Status:
Resolved
Priority:
High
Assignee:
Category:
Target version:
Start date:
2018-05-28
Due date:
% Done:

100%

Feature Branch:
feature/15622-linux-4.16
Type of work:
Code
Blueprint:

Starter:
Affected tool:
Deliverable for:

Description


Subtasks


Related issues

Related to Tails - Bug #15436: Consider upgrading Linux in Tails 3.8 Resolved 2018-03-22
Related to Tails - Bug #15681: Check getrandom() status and potential problems Resolved 2018-06-23
Blocks Tails - Feature #15139: Core work 2018Q2: Foundations Team Resolved 2018-01-01
Blocks Tails - Bug #15472: Rebase our Tor Browser AppArmor policy on top of torbrowser-launcher 0.2.9-2's Resolved 2018-03-28
Blocks Tails - Bug #15638: Remove deb.torproject.org sid APT source Resolved 2018-06-07
Blocks Tails - Bug #15116: X.Org does not start with some NVidia Maxwell and Pascal graphic cards Confirmed 2017-12-27

History

#1 Updated by intrigeri 2018-05-28 07:24:03

  • related to Bug #15436: Consider upgrading Linux in Tails 3.8 added

#2 Updated by intrigeri 2018-05-28 07:24:23

  • Feature Branch set to feature/15622-linux-4.16

#3 Updated by intrigeri 2018-05-28 07:27:55

#4 Updated by intrigeri 2018-05-29 14:50:08

  • Status changed from Confirmed to In Progress
  • Assignee changed from intrigeri to segfault
  • % Done changed from 0 to 50
  • QA Check set to Ready for QA

Passes the full test suite! (except 1 new scenario that I’ve never seen pass and “Playing HTML5 audio” that’s currently broken due to the remote server having exceeded their bandwidth limit).

Please review the tiny “code” changes and briefly test on whatever bare metal hardware you have handy, without spending more than 20 minutes on it.

This will only become urgence once 4.15 is removed from testing so I don’t mean to distract you from your other more urgent (though less exciting perhaps) work :)

#5 Updated by intrigeri 2018-06-05 17:42:50

  • Assignee changed from segfault to intrigeri
  • QA Check deleted (Ready for QA)

Before merging this, I’ll need to look into potential regressions caused by the getrandom() fix. Details:

#6 Updated by intrigeri 2018-06-23 07:19:34

  • related to Bug #15681: Check getrandom() status and potential problems added

#7 Updated by intrigeri 2018-06-23 07:21:28

  • Assignee changed from intrigeri to segfault
  • Priority changed from Normal to High
  • QA Check set to Ready for QA

Linux 4.15 was removed from sid so our devel branch now FTBFS.

So please review the tiny “code” changes and briefly test on whatever bare metal hardware you have handy, without spending more than 20 minutes on it.

> Before merging this, I’ll need to look into potential regressions caused by the getrandom() fix.

I’ll do that on Bug #15681.

#8 Updated by intrigeri 2018-06-26 06:39:49

  • blocks Bug #15472: Rebase our Tor Browser AppArmor policy on top of torbrowser-launcher 0.2.9-2's added

#9 Updated by intrigeri 2018-06-27 08:33:02

  • blocks Bug #15638: Remove deb.torproject.org sid APT source added

#10 Updated by intrigeri 2018-06-27 08:45:01

  • blocks Bug #15116: X.Org does not start with some NVidia Maxwell and Pascal graphic cards added

#11 Updated by segfault 2018-06-28 08:44:21

  • QA Check changed from Ready for QA to Pass

> So please review the tiny “code” changes and briefly test on whatever bare metal hardware you have handy, without spending more than 20 minutes on it.

Done, LGTM and boots on my hardware.

#12 Updated by segfault 2018-06-28 08:44:32

  • Assignee changed from segfault to intrigeri

#13 Updated by intrigeri 2018-06-28 13:17:39

  • Status changed from In Progress to Fix committed
  • % Done changed from 50 to 100

Thanks, merging!

#14 Updated by intrigeri 2018-06-28 13:29:31

  • Assignee deleted (intrigeri)

#15 Updated by intrigeri 2018-09-05 16:08:04

  • Status changed from Fix committed to Resolved