5 packages can be upgraded. Run 'apt list --upgradable' to see them. Listing... Gotowe kmod/unstable 26+20191223-1 amd64 [upgradable from: 26-3] libcpupower2/unstable 5.4.8-1 amd64 [upgradable from: 5.4.6-1] libkmod2/unstable 26+20191223-1 amd64 [upgradable from: 26-3] linux-cpupower/unstable 5.4.8-1 amd64 [upgradable from: 5.4.6-1] linux-libc-dev/unstable 5.4.8-1 amd64 [upgradable from: 5.4.6-1]
# LANG=C update-initramfs -k 5.4.8-towo.1-siduction-amd64 -u [583/3394]update-initramfs: Generating /boot/initrd.img-5.4.8-towo.1-siduction-amd64 depmod: ERROR: ../libkmod/libkmod.c:515 lookup_builtin_file() could not open builtin file '/var/tmp/mkinitramfs_mQ4YXU/lib/modules/5.4.8-towo.1-siduction-amd64/modules.builtin.bin' depmod: ERROR: ../libkmod/libkmod.c:515 lookup_builtin_file() could not open builtin file '/var/tmp/mkinitramfs_mQ4YXU/lib/modules/5.4.8-towo.1-siduction-amd64/modules.builtin.bin' depmod: ERROR: ../libkmod/libkmod.c:515 lookup_builtin_file() could not open builtin file '/var/tmp/mkinitramfs_mQ4YXU/lib/modules/5.4.8-towo.1-siduction-amd64/modules.builtin.bin(…)
...Control: severity -1 seriousraising the severity in case there can be a real major system breakage(not tested) and also because of the huge number of errors, which canhide important information (other errors...)....
On Wed, 2020-01-08 at 16:48 -0500, debian wrote:> so, what's to be done now? Marco d'Itri says that this error is > pointless, Bjørn says that this is normal and this behaviour is expected > sometimes (kmod looking for nonexistent stuff)> > is it just a harmless error "spam"? update the system as usual and just > ignore the error "waterfall" in the console? use the patch (the edited > line in /usr/sbin/mkinitramfs) and then update?Printing spurious error messages is a bug, and we will fix it (whetherin kmod or in initramfs-tools, is to be decided).But since (so far as I know) there hasn't been any regression in thefunctioning of the resulting initramfs, the bug doesn't need to befixed right this instant.Ben.