Bug #12736

live/vmlinuz not reproducible in some environments

Added by anonym 2017-06-19 10:12:49 . Updated 2017-06-23 08:27:58 .

Status:
Duplicate
Priority:
Normal
Assignee:
lamby
Category:
Build system
Target version:
Tails_3.1
Start date:
2017-06-19
Due date:
% Done:

100%

Feature Branch:
Type of work:
Research
Blueprint:

Starter:
Affected tool:
Deliverable for:
289

Description

See Feature #12608#note-18 for arnaud’s diffoscope report. There are also .torrent:s for the good ISO, and for arnaud’s.

The diff is huge, so the uncompressed data likely contains several differences.

Subtasks

History

#1 Updated by anonym 2017-06-19 10:24:36

  • Assignee set to lamby
  • QA Check set to Info Needed

Could you have a look?

#2 Updated by intrigeri 2017-06-19 10:24:42

Wow, a different kernel?! That’s seriously weird.

#3 Updated by anonym 2017-06-19 10:33:32

Actually, I must have made a mistake when I initially “determined” that the kernels differ, because they don’t. The only difference is:

│ -----------   0    0    0      1174503424 May 21 2017 [   2192 00]  filesystem.squashfs;1 
│ -----------   0    0    0        21043456 May 21 2017 [ 575680 00]  initrd.img;1 
│ -----------   0    0    0         4204320 May 21 2017 [ 585956 00]  vmlinuz.;1 
│ +----------   0    0    0      1175322624 May 21 2017 [   2192 00]  filesystem.squashfs;1 
│ +----------   0    0    0        20913280 May 21 2017 [ 576080 00]  initrd.img;1 
│ +----------   0    0    0         4204320 May 21 2017 [ 586292 00]  vmlinuz.;1


I.e. a shift in the extents since files written earlier had different sizes. So it’s probably just another instance of Bug #12737.

#4 Updated by intrigeri 2017-06-22 13:49:49

#5 Updated by lamby 2017-06-23 08:27:58

  • Status changed from Confirmed to Duplicate
  • % Done changed from 0 to 100

Agree re. “bleed” hypothesis. Closing as duplicate.