[Aptitude-devel] Bug#787663: aptitude forgets/clears manually set auto-installed-flags in several situations
Christoph Anton Mitterer
calestyo at scientia.net
Mon Feb 29 05:15:40 GMT 2016
On Sun, 2016-02-28 at 17:29 +0000, Manuel A. Fernandez Montecelo wrote:
> I just tried to reproduce this with upgrading "less" (some packages
> recommend it) and "install-info" (some packages depend on it) in
> with A flag set, but after proceeding to install but selecting "n" in
> apt-listchanges and then back to aptitude curses, the packages are
> marked for upgrade and with A flag.
> I tried the same with the command line, and with the same results --
> removal of A flag.
Sure that works...
> On the other hand, if I understood correctly, if nothing depends on
> krb5-k5tls on your system, you shouldn't have it marked as
It's a handy way to flag packages which I have just installed because
of something else (which however lacks a recommends or so)...
e.g. mkvtoolnix-gui used to not be recommended by mkvtoolnix, but I
installed the former only because of the later...
Or it can be used to scheduled packages for removal, but not doing it
Of course this makes just sense if auto-removal is not enabled, which
is however also perfectly fine to do.
> In fact, installing krb5-k5tls in my system and marking it as
> automatically installed, aptitude attempts to remove it immediately
> which is the right thing to do.
Sure.. but I don't think it's the right thing to remove the flag if I
manually set it.
Human is smarter than the machine... if he wants it he should get it.
-------------- next part --------------
A non-text attachment was scrubbed...
Size: 5930 bytes
Desc: not available
More information about the Aptitude-devel