On 2013-06-05 07:46:54 -0500, John Hasler wrote: > Andrei writes: > > Not necessarily. The package being installed might conflict with them > > (for good reasons) and aptitude doesn't always suggest the option with > > fewer removals. > > In that case Aptitude would be stating that it proposed to remove them, > not merely mentioning that they were no longer required. > > If I misunderstood and the OP meant the former it is most likely that > his new package requires the newest version of some library. Aptitude > will then propose the removal of anything that (directly or indirectly) > depends on that library but has not been upgraded to use the new > version. This is common in Sid and it is the reason packages do not > migrate to Testing until all their dependencies can be satisfied there.
aptitude sometimes proposes removals of many packages even when this is not the case. A few days ago, due to the hplip upgrade IIRC, aptitude proposed to remove hundreds of packages, while apt-get just proposed to remove libsnmp15 (and install libsnmp30 instead). So, the problem is not always sid, but aptitude. -- Vincent Lefèvre <vinc...@vinc17.net> - Web: <http://www.vinc17.net/> 100% accessible validated (X)HTML - Blog: <http://www.vinc17.net/blog/> Work: CR INRIA - computer arithmetic / AriC project (LIP, ENS-Lyon) -- 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/20130607091542.ga28...@ypig.lip.ens-lyon.fr
