On Mon, 02 Jun 2008, Daniel Burrows wrote: > It looks like the problem is a bug in the new code to fix > conflicts/provides/replaces. This tries to force the resolver to > resolve conflicts between a package and its replacement in favor of the > replacement by giving a rather large bonus to the score of solutions > that do so. You can verify that this is the cause of the problem by > passing "-o Aptitude::ProblemResolver::FullReplacementScore=0" and > "-o Aptitude::ProblemResolver::UndoFullReplacement=0" to the program at > the command-line: it will avoid the downgrades and produce the solution > that keeps the packages at the current version first instead.
Thanks for the quick response and analysis! I can't check it any more as the temporary problem of twe two packages being not in sync disappeared on my machine. > Although I haven't had any other complaints about this, I think it's > probably serious enough to warrant another bugfix upload if I can > squeeze the current one into lenny, since it will cause the resolver to > randomly do inexplicably stupid things. I agree that we should push this fix to lenny. Cheers, -- Raphaël Hertzog Le best-seller français mis à jour pour Debian Etch : http://www.ouaza.com/livre/admin-debian/ -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
