Comment 9 for bug 2012750

@waveform, sorry to bother late in the release calendar. It isn't urgent, I'm just trying to work around it on my end, but I can manually downgrade the function file until this is addressed cleanly.

This issue is due to my changing of a file path in the DEBIAN/postinst hook portion of my kernel install:

version=$kver
image_path=/boot/vmlinuz-\$version

# Install kernel (This avoids an issue if /boot is fat32.)
mount -o remount,rw /boot 2>/dev/null || true
cp /usr/share/rpikernelhack/vmlinuz-"$kver" \$image_path

But this is due to a potentially fat32 boot partition not being supported for installs of files by dpkg.

It is explicitly suggested to use a postinst hook to install on such partitions here:

https://wiki.debian.org/Teams/Dpkg/FAQ#Q:_What_are_the_filesystem_requirements_by_dpkg.3F

So ideally, the get_kernel_status function would handle dpkg-query not finding the kernel in the originally installed location.