On Friday, 15 de April de 2005 14:52, Daniel Burrows shaped the electrons to shout: > I think I found the problem. Normally when aptitude does an upgrade, > it first marks all packages for upgrade, then does a second pass to > resolve dependencies. However, for some reason the command-line > interface uses a *different* algorithm to set up the upgrade, resolving > dependencies as it marks things for upgrade. The result is that > versioned ORed dependencies (or more generally, dependencies only > resolved by the upgraded version of a package) might be resolved by > installing a new package, when they could be resolved by upgrading an > existing package. > > The difference between what happens in aptitude and what happens in > apt-get is likely due to the fact that (a) aptitude follows Recommends > and apt-get doesn't, and (b) aptitude processes packages in a different > order from apt-get.
I think it's still a little worse. In my caso aptitude seems to ignore dependencies resolved by local [already] installed packages. -- ricardo galli GPG id C8114D34 http://mnm.uib.es/gallir/ Listening: Talking Heads - Heaven -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
