I think I have some more information about this bug, although I'm not sure if it's actually the same.
sudo aptitude install libc6-amd64 [...] The following packages have unmet dependencies: libc6-amd64: Depends: libc6 (= 2.3.6.ds1-13etch5) but 2.7-9 is installed. [...] The following actions will resolve these dependencies: Install the following packages: libc6-amd64 [2.7-9 (unstable, now)] [...] Accept this solution? [Y/n/q/?] No packages will be installed, upgraded, or removed. Note that libc6-amd64 is "(unstable, now)". Indeed: rc libc6-amd64 2.7-9 GNU C Library: 64bit Shared libraries for AM So, aptitude initially decided to not install the stable version (from Default-Release) due to dependencies, calculated a solution, but then decided that the installation would do nothing since it wasn't in state "removed". However I think the correct check test would be closer to "if package in state *installed*". -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
