[ I am putting this back on d-u; please make sure to reply to the list. ] On Sat, Jun 05, 2010 at 16:05:17 +0100, Vasco Costa wrote: > On Sat, 2010-06-05 at 09:55 +0200, Florian Kulzer wrote: > > Your first hypothesis is most likely the correct one; the "optional > > dependency" that keeps the package on your system can be a "recommends" > > or even a "suggests" of another package, depending on how you have > > configured aptitude. > > I've just proved my first hypothesis wrong. I haven't changed any > configuration options, so both aptitude::Keep-Recommends and > aptitude::Keep-Suggests are set to their default value which is false.
The last time I configured aptitude, aptitude::Keep-Recommends was true by default. > I really have no idea why this is happening. As an example let me show > what happens with the mplayer package. > > When I install mplayer the following deps are installed: > > libfribidi0 > liblzo2-2 > libmpcdec3 > libopenal1 > libxvmc1 > mplayer-skin-blue > > However if I immediately run aptitude remove/purge mplayer following the > install only these deps are removed: > > liblzo2-2 > libmpcdec3 > libopenal1 > libxvmc1 > mplayer-skin-blue > > Notice that they are all removed except for libfribidi0. In this > particular case it's quite easy to remove it manually, but on packages > with over 100 deps it gets annoying. > > Is there anything I can try in order to understand why libfribidi0 in > particular isn't being removed? You can ask aptitude directly: aptitude why libfribidi0 -- Regards, Florian -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20100605163056.ga6...@isar.localhost
