Package: flash-kernel Version: 3.110+reform20260806T212135Z+1 Severity: serious Tags: patch
Hi, with Linux 7.2, flash-kernel fails like this: Processing triggers for initramfs-tools (0.151) ... update-initramfs: Generating /boot/initrd.img-7.2.3-mnt-reform-arm64 cryptsetup: WARNING: Couldn't determine root device Label reformsdroot not found in /dev/disk/by-label Warning: root device LABEL=reformsdroot does not exist W: Couldn't identify type of root file system 'LABEL=reformsdroot' for fsck hook W: unable to deduce target machine for reform initramfs-hook dpkg-query: no packages found matching run-parts: /etc/initramfs/post-update.d//flash-kernel exited with return code 1 dpkg: error processing package initramfs-tools (--configure): old initramfs-tools package postinst maintainer script subprocess failed with exit status 1 The problem is worked around here: https://salsa.debian.org/installer-team/flash-kernel/-/merge_requests/86 Debian Linux 7.2 and later ships vmlinuz in /usr/lib/modules/$ver/vmlinuz "linux-version list" lists the kernels matching the glob "/boot/vmlinu[xz]-*" but since Debian Linux 7.2, the location of vmlinuz was moved from /boot into /usr/lib/modules/$ver. The binary package also changed from linux-image-$ver to linux-binary-$ver in 6.19. As a result, the function get_kernel_status would error out with kernel 7.2 because there is no longer any package shipping "/boot/vmlinu[xz]-*". This commit works around this problem but there are open questions: 1. why does this function not just set pkg=linux-image-$ver or pkg=linux-binary-$ver 2. is this function expected to return linux-image-$ver or, for kernels 6.19 and later, linux-binary-$ver (this is the new behaviour now) 3. is it sufficient to wait for the state being "installed" for linux-binary-$ver or should linux-image-$ver be "installed"? 4. is it okay that the new version of this function disconnects the path to vmlinuz from the output of "linux-version list"? The path in /boot will not be populated at unpack time. 5. is the use of "linux-version list" not wrong starting with kernel 7.2 because linux-binary-$ver does no longer unpack the kernel to /boot? Thanks! cheers, josch
