On Sat, Nov 14, 2026 at 22:05:35 -0700, Charles Curley wrote:
> On Sat, 14 Nov 2026 21:51:35 -0500
> Greg Wooledge <[email protected]> wrote:
> > The setting you're looking at affects autoremove. It doesn't
> > *trigger* an autoremove. You still need to run it yourself.
>
> Now you have me mystified. If I don't set
> APT::NeverAutoRemove::KernelCount then upgrades automatically install a
> new kernel. (I have linux-image-amd64 installed.) They also remove an
> old one, leaving me with the default net two kernels.
>
> I don't think I have ever run "apt autoremove". I just did so on a
> machine with five kernels installed; none were removed.
Hmm. Maybe it's a difference between apt-get and apt, then? I usually
use apt-get, and it definitely doesn't do an autoremove for me.
hobbit:~$ apt-get -s upgrade
NOTE: This is only a simulation!
[...]
The following packages were automatically installed and are no longer required:
enchant-2 ghp-import gir1.2-gtk-2.0 girepository-tools gsfonts gsfonts-x11
[...]
Use 'apt autoremove' to remove them.
0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.
I don't do autoremoves on that system. On others where I do use it, it
has always (so far) kept only the 2 latest kernels, as expected.
> The current linux-image-amd64 depends on
> linux-image-6.12.117+deb13-amd64. So if autoremove worked on kernels,
> should it have removed all the kernels except
> linux-image-6.12.117+deb13-amd64? Maybe it makes an exception for
> kernels?
Well... there's /etc/apt/apt.conf.d/01autoremove which contains
NeverAutoRemove
{
"^firmware-linux.*";
"^linux-firmware$";
"^linux-image-[a-z0-9]*$";
"^linux-image-[a-z0-9]*-[a-z0-9]*$";
};
So if you've got custom kernels whose package names match one of those
regexes, they're untouchable.
If your kernels are from Debian (and therefore don't match any of those
regexes), then they should be counted by the KernelCount variable as far
as I'm aware.
How *exactly* did you configure this variable?