Your message dated Fri, 13 Mar 2020 19:28:00 -0600
with message-id <[email protected]>
and subject line Isn't this bug fixed with version 1.20171006 ?
has caused the Debian Bug report #864945,
regarding wrong sort order in kernel postinst hook
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact [email protected]
immediately.)
--
864945: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=864945
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: raspi3-firmware
Version: 1.20170317-4
the sort commands utilized for searching the most actual kernel in
/etc/kernel/postinst.d/raspi3-firmware are not using option
--version-sort. this doesn't work for updates e.g. from 4.9 to 4.12.
a patch to fix this issue is included.
diff --git a/debian/kernel/postinst.d/raspi3-firmware b/debian/kernel/postinst.d/raspi3-firmware
index ca4d158..38cc69d 100755
--- a/debian/kernel/postinst.d/raspi3-firmware
+++ b/debian/kernel/postinst.d/raspi3-firmware
@@ -22,13 +22,13 @@ if ! ischroot; then
fi
fi
-latest_kernel=$(ls -1 /boot/vmlinuz-* | grep -v '\.dpkg-bak$' | sort -r | head -1)
+latest_kernel=$(ls -1 /boot/vmlinuz-* | grep -v '\.dpkg-bak$' | sort -V -r | head -1)
if [ -z "$latest_kernel" ]; then
echo "raspi3-firmware: no kernel found in /boot/vmlinuz-*, cannot populate /boot/firmware"
exit 0
fi
-latest_initrd=$(ls -1 /boot/initrd.img-* | grep -v '\.dpkg-bak$' | sort -r | head -1)
+latest_initrd=$(ls -1 /boot/initrd.img-* | grep -v '\.dpkg-bak$' | sort -V -r | head -1)
if [ -z "$latest_initrd" ]; then
echo "raspi3-firmware: no initrd found in /boot/initrd.img-*, cannot populate /boot/firmware"
exit 0
--- End Message ---
--- Begin Message ---
Package: raspi3-firmware
Version: 1.20171006-1
Replying to quite an old bug. Yes, Diedrik de Haas is completely
correct - This bug was dealt with a long time ago, only it was not
acknowledged.
Thanks!
--- End Message ---
