[Aptitude-devel] Bug#567722: Apt::AutoRemove::InstallRecommends etc.

Manuel A. Fernandez Montecelo manuel.montezelo at gmail.com
Sun Nov 8 00:51:21 UTC 2015

Control: tags -1 + moreinfo unreproducible

2010-01-30 22:14 jidanni at jidanni.org:
>Package: aptitude
>Severity: wishlist
>Another blurry bug report about a blurry subject. Sorry.

So blurry that I struggle to make sense of it after many minutes
re-reading it...

>We see some inconsistencies
>$ strings `which aptitude`|grep Recomm

The messages are different now, but I don't know why do you think that
they are inconsistent.  There are different options for different parts
of apt (normal "install recommands" and "keep recommends when
autoremoving" -- which are different cases).  Even if they were
inconsistent, there's little in aptitude that we can do about that.

And the aptitude ones are for different cases as well.

>Also e.g., for Apt::AutoRemove::InstallRecommends one cannot tell if -R
>means setting it to false or true.
> [...]
>Anyway, After update; but before full-upgrade
>$ aptitude why iso-codes
>i   apt-listchanges Depends    python-apt
>i A python-apt      Recommends iso-codes
>After full-upgrade
>i   midori                          Depends libwebkit-1.0-2 (>= 1.1.15)
>i A libwebkit-1.0-2                 Depends libgstreamer-plugins-base0.10-0 (>= 0.10.16)
>i A libgstreamer-plugins-base0.10-0 Depends iso-codes
>So one needs to upgrade to see the real why...

Again, the report is quite diffuse about the options used and what is
confusing, and the exact commands used.

Also, perhaps reading apt's documentation on that option would help to
clear things up, or even aptitude's:


Manuel A. Fernandez Montecelo <manuel.montezelo at gmail.com>

More information about the Aptitude-devel mailing list