Dear Maintainer,
Previously there was a kernel upgrade from -29 to -30. I rebooted
to -30 and everthing was fine. Then yesterday, I did an upgrade to
fix a rsync regression. After that upgrade, needrestart reported
that the running kernel (-30) was not the expected version. It said
I should consider rebooting in order to get expected kernel version -29.
Today there was another upgrade (freedombox this time) after which
needrestart gave the same erroneous message concerning versions 29
and 30.
uname -a returns:
Linux freedombox 6.1.0-30-marvell #1 Debian 6.1.124-1 (2025-01-12) armv5tel GNU/Linux
apt-cache policy shows the following for kernels -29 and -30
linux-image-6.1.0-29-marvell:
Installed: 6.1.123-1
Candidate: 6.1.123-1
Version table:
*** 6.1.123-1 500
500 http://192.168.1.10:3142/deb.debian.org/debian bookworm/main armel Packages
100 /var/lib/dpkg/status
linux-image-6.1.0-30-marvell:
Installed: 6.1.124-1
Candidate: 6.1.124-1
Version table:
*** 6.1.124-1 500
500 http://192.168.1.10:3142/deb.debian.org/debian bookworm-updates/main armel Packages
100 /var/lib/dpkg/status
I expect that needrestart recognise that -30 is newer than -29 and that there is
therefor no need to encourage a reboot.