From: Sjors G. <mai...@da...> - 2011-06-06 05:11:22
|
Hi Alexander, I've looked a bit into the issues you e-mailed about a while ago. Sorry it took me this long to respond, I've had a lot to do lately... > Hmm, seems like the AutoRemover destroyed something which really > shouldn't happen. Please file a bug report against apt. These lines are printed just before every installation, just after apt checks if it's going to do some automatic removal of old packages. These specific lines are printed when after this process, there's a "broken count" in the current installation cache, i.e. when there's a broken package configuration. The breakage is then subsequently printed: > The following information may help to resolve the situation: > > The following packages have unmet dependencies: > gmp: Conflicts: gmp5 but 5.0.2-1 is to be installed > gmp5: Conflicts: gmp but 4.3.2-8 is to be installed This seems like a good reason to bail out! Two packages Conflict with each other, they are both installed, and apt can't decide which one to keep. It just seems unfortunate, but I'm not sure here, that this error appears right after the autoremoval step; it doesn't seem to actually /be/ that piece of code that causes this broken situation, apt just assumes it starts clean and gives this error. Apt 0.5 simply seems oblivious to the problem, probably leaving gmp in the "not upgraded" section: > Reading Package Lists... Done > Building Dependency Tree... Done > The following NEW packages will be installed: > gmp5 > 11 packages upgraded, 1 newly installed, 0 to remove and 16 not upgraded. I'm not trying to be an obsessed apt-0.7 supporter, but I think apt-0.7 isn't to blame here. I think there are two possibilities here: 1) there is a difference in what packages apt-0.5 and apt-0.7 think are installed, or 2) old-apt doesn't know about this conflict or it simply ignores it. To make sure (1) is not the problem, could you reproduce this situation, and then check with both versions of apt what versions of gmp and gmp5 are installed? If the conflict doesn't exist in apt-0.5 and it does on apt-0.7, further research is required; on the other hand, if we can see gmp and gmp5 are conflicting but still apt-0.5 leaves them around, then we can actually see this as a feature in apt-0.7, not a bug! ;-) Please let me know any new results! Thanks, Sjors |