/lib/modules/*/modules.* not reproducible in some environments
Originally created by @anonym on #12741 (Redmine)
See #12608 (comment 44739) for arnaud’s diffoscope report. There are also
.torrent
:s for the good ISO, and for arnaud’s.
Ignoring the .bin
files, diffoscope shows something interesting:
├── /lib/modules/4.9.0-3-amd64/modules.alias
│ │ @@ -19383,8 +19383,7 @@
│ │ alias vport-type-3 vport_gre
│ │ alias net-pf-40 vmw_vsock_vmci_transport
│ │ alias vmware_vsock vmw_vsock_vmci_transport
│ │ alias virtio:d00000013v* vmw_vsock_virtio_transport
│ │ alias fs-vboxsf vboxsf
│ │ alias pci:v000080EEd0000BEEFsv*sd*bc*sc*i* vboxvideo
│ │ alias pci:v000080EEd0000CAFEsv00000000sd00000000bc*sc*i* vboxguest
│ │ -alias fs-aufs aufs
[...]
── /lib/modules/4.9.0-3-amd64/modules.dep
│ │ @@ -3395,8 +3395,7 @@
│ │ kernel/lib/mpi/mpi.ko:
│ │ kernel/lib/asn1_decoder.ko:
│ │ kernel/lib/oid_registry.ko:
│ │ kernel/virt/lib/irqbypass.ko:
│ │ updates/vboxsf.ko: updates/vboxguest.ko
│ │ updates/vboxvideo.ko: updates/vboxguest.ko kernel/drivers/gpu/drm/ttm/ttm.ko kernel/drivers/gpu/drm/drm_kms_helper.ko kernel/drivers/gpu/drm/drm.ko
│ │ updates/vboxguest.ko:
│ │ -kernel/fs/aufs/aufs.ko:
I wonder: is this what you’d expect if depmod
wasn’t run after the
aufs module was built?
Attachments
- tails-amd64-3.0~rc2.iso.apt-sources
- tails-amd64-3.0~rc2.iso.build-manifest
- tails-amd64-3.0~rc2.iso.packages
- tails-amd64-3.0~rc2.iso.buildlog
- tails-amd64-3.0~rc2.iso.apt-sources
- tails-amd64-3.0~rc2.iso.build-manifest
- tails-amd64-3.0~rc2.iso.packages
- tails-amd64-3.0~rc2.iso.buildlog
- buildlog.diff
- 2017-07-10-build-make.log
- 2017-07-10-tails-dkms-hook.log
- diff84.tails-3.0.1.arnaud.html
Parent Task: #5630 (closed)
Related issues
-
Blocked by #13480 (closed)
Edited by anonym