On Sun, 15 Nov 2026 08:42:23 -0500
Greg Wooledge <[email protected]> wrote:

> > 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.

root@peregrine:~# pre ux-im ; uname -r
linux-image-6.12.111+deb13-amd64        6.12.111-1              amd64
linux-image-6.12.113+deb13-amd64        6.12.113-1              amd64
linux-image-6.12.115+deb13.1-amd64      6.12.115-2              amd64
linux-image-6.12.116+deb13-amd64        6.12.116-1              amd64
linux-image-6.12.117+deb13-amd64        6.12.117-1              amd64
linux-image-amd64       6.12.117-1              amd64
6.12.117+deb13-amd64
root@peregrine:~# apt-get -s upgrade
Reading package lists... Done
Building dependency tree... Done
Reading state information... Done
Calculating upgrade... Done
0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.
root@peregrine:~# apt-get -s autoremove 
Reading package lists... Done
Building dependency tree... Done
Reading state information... Done
0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.
root@peregrine:~# 




> 
> > 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.

No custom kernels here. Nor have I mucked with NeverAutoRemove.

> 
> How *exactly* did you configure this variable?

root@peregrine:/etc/apt/apt.conf.d# cat 40neverAutoRemove
# man apt.conf; less /usr/share/doc/apt/examples/configure-index

APT::NeverAutoRemove::KernelCount "3";
root@peregrine:/etc/apt/apt.conf.d# 



-- 
Does anybody read signatures any more?

https://charlescurley.com
https://charlescurley.com/blog/

Reply via email to