On Fri, Mar 21, 2008 at 02:11:52PM -0400, Justin Pryzby <[EMAIL PROTECTED]> was heard to say: > 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*".
It would be handy if you could run that with "-o Aptitude::ProblemResolver::Trace-File=some-file" and send the resulting file to this bug. (that generates a cut-down version of the package cache plus some information about how the resolver was invoked, hopefully fairly small) Daniel -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
