At some point in the New Year following a full-upgrade, my system ceased to autoremove the oldest kernel. It now wants to remove the running kernel, which I deny. Following a reboot into the newly installed kernel, nothing is to be removed.
My update procedure previous was apt update && apt full-upgrade && apt autoremove && reboot
In one of my backups I find the behavior I believe I used to have. This under apt kernel postinst.d apt-auto-removal
and is
#!/bin/sh
set -e
# Mark as not-for-autoremoval those kernel packages that are:
# - the currently booted version
# - the kernel version we've been called for
# - the latest kernel version (as determined by debian version number)
# - the second-latest kernel version
#
# In the common case this results in two kernels saved (booted into the
# second-latest kernel, we install the latest kernel in an upgrade), but
# can save up to four. Kernel refers here to a distinct release, which can
# potentially be installed in multiple flavours counting as one kernel.
I do not find this in my current running system. Has the procedure changed? I did come across a thread under Upgrade Warnings that I thought was directly related to this, but the addition of the apt-config-siduction file which spawned the "80siduction" did not change things for me.
So if this is the expected behavior, I will remove the kernels manually.
Thoughts appreciated.
Cliff