On Sun, May 02, 2021 at 01:42:29PM +0200, Axel Beckert wrote:
> Control: notfound 902652 0.8.13-3
> Contyrol: severity 902652 norma;
>
> Dear Jidanni,
>
> > Proof that aptitude is not ready for
> >
> > /usr/share/doc/apt/NEWS.Debian.gz
> > apt (2.1.16) unstable; urgency=medium
> >
> > Automatically remove unused kernels on apt {dist,full}-upgrade. To
> > revert
> > to previous behavior, set APT::Get::AutomaticRemove::Kernels to false
> > or
> > pass --no-auto-remove to the command. apt-get remains unchanged.
>
> Proof that this is wrong:
>
> That feature wasn't present in apt 1.4.8 which was present when the
> original bug was reported. Hence reverting your changes to this bug
> report.
>
> Feel free to report a separate bug report for compatibility with the
> 2.1.16 apt changes.
>
> And wrt. to
> https://bugs.launchpad.net/ubuntu/+source/aptitude/+bug/1772688:
> Please note that apt-get hasn't changed either and behaves differently
> that apt. And nobody stated that aptitude will follow apt and not
> apt-get. (Nobody has stated the opposite either, though, but it's
> obviously the default.)
There is a bug in aptitude, so to speak, as it protects all linux
images, it literally protects like ~n^linux-image or something like
that by supplying its own root set function somewhere, when it should
just rely on APT's default root set function.
That said, that's a post-freeze topic I reckon.
--
debian developer - deb.li/jak | jak-linux.org - free software dev
ubuntu core developer i speak de, en
