On Wed, Jun 04, 2008 at 08:11:16AM +0200, Raphael Hertzog <[EMAIL PROTECTED]> was heard to say: > 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. > > Confirmed today with a similar problem with gnupg. Passing those two > options made it select the right solution.
Does the patch I sent fix the problem as well? (passing those two options just disables the new code; my patch actually fixes it) Daniel -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
