Control: severity -1 important Hi Karsten,
Quoting Karsten Merker (2019-04-27 17:40:20)
> when trying to include a kernel image in the package list for
> mmdebstrap, mmdebstrap fails when running the deferred trigger for
> update-initramfs. The effect is independent of the architecture
> (tested on amd64, armhf and riscv64). When doing a standard install
> without the "--include" parameter, switching to the chroot and
> manually installing the same kernel package everything works without
> problems.
thank you for your bug report!
This is very interesting and weird... The biggest problem is:
> Failure log
> ===========
> $ sudo mmdebstrap --aptopt='Acquire::http { Proxy "http://127.0.0.1:3142";; }'
> --architectures=amd64 --include="linux-image-amd64" sid /tmp/amd64-chroot
> "deb http://deb.debian.org/debian/ sid main"
this works for me without any issues. I'm running the exact same command (I
also have apt-cacher-ng installed locally).
My only clue to this riddle is this:
> Setting up linux-image-4.19.0-4-amd64 (4.19.28-2) ...
> I: /vmlinuz.old is now a symlink to boot/vmlinuz-4.19.0-4-amd64
> I: /initrd.img.old is now a symlink to boot/initrd.img-4.19.0-4-amd64
> I: /vmlinuz is now a symlink to boot/vmlinuz-4.19.0-4-amd64
> I: /initrd.img is now a symlink to boot/initrd.img-4.19.0-4-amd64
> /etc/kernel/postinst.d/initramfs-tools:
> update-initramfs: Generating /boot/initrd.img-4.19.0-4-amd64
> W: Possible missing firmware /lib/firmware/rtl_nic/rtl8107e-2.fw for module
> r8169
> W: Possible missing firmware /lib/firmware/rtl_nic/rtl8107e-1.fw for module
> r8169
> W: Possible missing firmware /lib/firmware/rtl_nic/rtl8168h-2.fw for module
> r8169
> W: Possible missing firmware /lib/firmware/rtl_nic/rtl8168h-1.fw for module
> r8169
> W: Possible missing firmware /lib/firmware/rtl_nic/rtl8168g-3.fw for module
> r8169
> W: Possible missing firmware /lib/firmware/rtl_nic/rtl8168g-2.fw for module
> r8169
> W: Possible missing firmware /lib/firmware/rtl_nic/rtl8106e-2.fw for module
> r8169
> W: Possible missing firmware /lib/firmware/rtl_nic/rtl8106e-1.fw for module
> r8169
> W: Possible missing firmware /lib/firmware/rtl_nic/rtl8411-2.fw for module
> r8169
> W: Possible missing firmware /lib/firmware/rtl_nic/rtl8411-1.fw for module
> r8169
> W: Possible missing firmware /lib/firmware/rtl_nic/rtl8402-1.fw for module
> r8169
> W: Possible missing firmware /lib/firmware/rtl_nic/rtl8168f-2.fw for module
> r8169
> W: Possible missing firmware /lib/firmware/rtl_nic/rtl8168f-1.fw for module
> r8169
> W: Possible missing firmware /lib/firmware/rtl_nic/rtl8105e-1.fw for module
> r8169
> W: Possible missing firmware /lib/firmware/rtl_nic/rtl8168e-3.fw for module
> r8169
> W: Possible missing firmware /lib/firmware/rtl_nic/rtl8168e-2.fw for module
> r8169
> W: Possible missing firmware /lib/firmware/rtl_nic/rtl8168e-1.fw for module
> r8169
> W: Possible missing firmware /lib/firmware/rtl_nic/rtl8168d-2.fw for module
> r8169
> W: Possible missing firmware /lib/firmware/rtl_nic/rtl8168d-1.fw for module
> r8169
> Setting up linux-image-amd64 (4.19+104) ...
> Setting up tasksel (3.52) ...
> Setting up tasksel-data (3.52) ...
> Processing triggers for libc-bin (2.28-9) ...
> Processing triggers for systemd (241-3) ...
> Processing triggers for initramfs-tools (0.133) ...
> update-initramfs: Generating /boot/initrd.img-4.19.0-4-amd64
> W: Possible missing firmware /lib/firmware/rtl_nic/rtl8107e-2.fw for module
> r8169
> W: Possible missing firmware /lib/firmware/rtl_nic/rtl8107e-1.fw for module
> r8169
> W: Possible missing firmware /lib/firmware/rtl_nic/rtl8168h-2.fw for module
> r8169
> W: Possible missing firmware /lib/firmware/rtl_nic/rtl8168h-1.fw for module
> r8169
> W: Possible missing firmware /lib/firmware/rtl_nic/rtl8168g-3.fw for module
> r8169
> W: Possible missing firmware /lib/firmware/rtl_nic/rtl8168g-2.fw for module
> r8169
> W: Possible missing firmware /lib/firmware/rtl_nic/rtl8106e-2.fw for module
> r8169
> W: Possible missing firmware /lib/firmware/rtl_nic/rtl8106e-1.fw for module
> r8169
> W: Possible missing firmware /lib/firmware/rtl_nic/rtl8411-2.fw for module
> r8169
> W: Possible missing firmware /lib/firmware/rtl_nic/rtl8411-1.fw for module
> r8169
> W: Possible missing firmware /lib/firmware/rtl_nic/rtl8402-1.fw for module
> r8169
> W: Possible missing firmware /lib/firmware/rtl_nic/rtl8168f-2.fw for module
> r8169
> W: Possible missing firmware /lib/firmware/rtl_nic/rtl8168f-1.fw for module
> r8169
> W: Possible missing firmware /lib/firmware/rtl_nic/rtl8105e-1.fw for module
> r8169
> W: Possible missing firmware /lib/firmware/rtl_nic/rtl8168e-3.fw for module
> r8169
> W: Possible missing firmware /lib/firmware/rtl_nic/rtl8168e-2.fw for module
> r8169
> W: Possible missing firmware /lib/firmware/rtl_nic/rtl8168e-1.fw for module
> r8169
> W: Possible missing firmware /lib/firmware/rtl_nic/rtl8168d-2.fw for module
> r8169
> W: Possible missing firmware /lib/firmware/rtl_nic/rtl8168d-1.fw for module
> r8169
> E: run_chroot failed: E: /usr/sbin/chroot /tmp/amd64-chroot env
> --unset=APT_CONFIG --unset=TMPDIR apt-get --yes install
> -oAPT::Status-Fd=<$fd> -oDpkg::Use-Pty=false passwd isc-dhcp-client fdisk
> debconf gpgv netbase logrotate tasksel-data debconf-i18n kmod bsdmainutils
> apt-utils vim-common libpam-runtime adduser less nano ifupdown
> readline-common linux-image-amd64 systemd-sysv dmidecode iproute2
> debian-archive-keyring whiptail libpam-modules init tzdata e2fsprogs rsyslog
> apt mawk procps vim-tiny tasksel iputils-ping cpio sensible-utils iptables
> isc-dhcp-common gdbm-l10n mount libpam-modules-bin cron udev systemd failed
as one can see, there is no error at all in the output you pasted that comes
from apt or any maintainer script. My theory is that the script fails because
some of the output lines start with a "W:". The problem with that is, that
mmdebstrap interprets "W:" lines as errors because in certain circumstances,
apt communicates errors to the user not by its exit status but by "W:"
messages. This has been reported to apt as #778357, #776152, #696335 and
#745735 but is just a wontfix unfortunately. I guess what should be done here,
is to not handle "W:" lines that way for any operations that are not "apt-get
update". Notice also how in your last log, when you install linux-image-amd64,
update-initramfs does not output any "W:" lines. I have no idea why though...
Thanks!
cheers, josch
signature.asc
Description: signature
