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. Daniel -- /------------------- Daniel Burrows <[EMAIL PROTECTED]> ------------------\ | First they ignore it, then they laugh at it, | | then they say they knew it all along. | \------ (if (not (understand-this)) (go-to http://www.schemers.org)) -------/
pgpSreHqcmMx9.pgp
Description: PGP signature
