Tails

#1 Updated by intrigeri 2019-01-26 07:03:12

• blocks Feature #15507: Core work 2019Q1: Foundations Team added

#2 Updated by intrigeri 2019-01-26 07:10:18

• Status changed from Confirmed to In Progress
• Assignee set to intrigeri
• % Done changed from 0 to 10
• Feature Branch set to feature/16390-linux-4.19.0-2+force-all-tests

#3 Updated by intrigeri 2019-01-26 09:14:04

• QA Check set to Ready for QA

(To force build reproducibility testing in our CI.)

#4 Updated by intrigeri 2019-01-26 17:36:45

• Assignee changed from intrigeri to lamby

Across 2 full test suite runs on our shared Jenkins, all scenarios passed at least once except one MAC spoofing failure notification step and Totem’s “Watching a WebM video over HTTPS”. These ones fail almost all the time on Jenkins these days so this looks good.

I did not test on bare metal: the 3.13 dev cycle has not started yet so I’m sure we’ll have plenty of opportunities to exercise this kernel upgrade in the next 1.5 month. And anyway, given devel uses non-frozen APT snapshots, Without the ABI bump, we would have got this kernel upgrade transparently, so this ticket + PR are mostly a formality.

Please review and I’ll merge into devel, so work targeted at 3.13 can resume.

Thanks in advance!

#5 Updated by intrigeri 2019-01-28 15:36:02

• blocks Feature #16138: Ship a pre-compiled AppArmor binary cache added

#6 Updated by lamby 2019-01-30 10:05:31

• Assignee changed from lamby to intrigeri

Sorry but some stuff has come up and I will no longer be able to do this. :(

#7 Updated by anonym 2019-01-30 11:59:40

• Target version changed from Tails_3.12 to Tails_3.13

#8 Updated by anonym 2019-01-31 11:58:04

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

Applied in changeset commit:tails|f17a48094531706b0f920dc44666e66d7f260ca0.

#9 Updated by anonym 2019-01-31 11:58:51

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

intrigeri wrote:
> I did not test on bare metal: the 3.13 dev cycle has not started yet so I’m sure we’ll have plenty of opportunities to exercise this kernel upgrade in the next 1.5 month. And anyway, given devel uses non-frozen APT snapshots, Without the ABI bump, we would have got this kernel upgrade transparently, so this ticket + PR are mostly a formality.

That’s what I thought, too, and was about to just merge this (only looking at code and automated test suite results). Nevertheless I spent some spare cycles testing it on two of my machines without issue. Merged!

#11 Updated by intrigeri 2019-02-11 17:33:20

• related to Bug #16371: Upgrade to Linux 4.19.16-1 in 3.13 added

#12 Updated by intrigeri 2019-02-13 15:34:37

• Status changed from Fix committed to Resolved