On Wed, Mar 21, 2012 at 05:01:57PM +0100, Alberto Fuentes wrote: > On 21/03/12 07:08, Chris Bannister wrote: > >Remember, Aptitude's "resolver system" is different to apt-get's > > I think the problem is not the the resolver (apt-get and aptitude > should get dependences about the same if not problem found, and > therefore "aptitude full-upgrade" should do the same as "apt-get > dist-upgrade" thats it, bring all packages up to date following the > pinning system and install and remove packaged when needed.
It seems so simple doesn't it. > Im not sure (nor im sure how to check it if thats the case) but I > think it may have to do with the database of how packages where > installed. If you install some packages with aptitude and others > with apt-get and then remove a third one with aptitude again, MAYBE > the auto and manual installation flag in some packages goes crazy as > they are handled in separate db (AAFAIK) That used to be the case. If you do some research (duckduckgo.com¹ can help here) you will find that a) package dependency resolution is not an easy task and b) apt-get and aptitude no longer use different databases. ¹ http://donttrack.us/ -- "Religion is excellent stuff for keeping common people quiet." -- Napoleon Bonaparte -- 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/20120323130942.GA13546@tal
