Hi there. I figured the cause out a few days ago, then had an attack of family...
Anyway, this is a side-effect of aptitude calculating upgrades mutatively -- that is, it sets its internal state to where the upgrade would go (which causes unused packages to be removed, including the old console-setup one), then computes a resolver solution. The resolver solution requires satisfying a dependency on the two console-setup packages, and for some reason (which will be easy to find once I sit down and investigate this) it decides to install the one that's not installed. This happens on a laptop where I haven't held anything back. The mechanism exists to do a non-mutative upgrade calculation, I just hadn't hooked it up to the command-line. That could solve half the problem. I'd also like to see why the resolver isn't just canceling the automatic removal -- that ought to be preferred to installing a new package. Daniel -- To UNSUBSCRIBE, email to [email protected] with a subject of "unsubscribe". Trouble? Contact [email protected]
