On Tue, 2010-01-19 at 10:07 -0800, Daniel Burrows wrote: > > The main difficulty in cases like this is getting the algorithm to > properly balance removals with upgrades. However, it looks like the > old scoring system works just fine here. This command line: > > aptitude -o 'aptitude::problemresolver::remove-tier=10000' -s dist-upgrade > > tells aptitude that it shouldn't force removals to appear after > keeps. The resulting solution looks mostly reasonable:
Yes, that's much better. I was about to report that it gets it right for the texlive transition on every point, apart from wanting to remove dvipdfmx. But then I saw that the new texlive-base says it now provides dvipdfmx. So this solution is just fine. (What a weird transition the texlive guys have done.) The upgrade with aptitude::problemresolver::remove-tier=10000 then proceeds happily. texlive is now upgraded to 2009. > > I have some ideas on how to use the tier mechanism in a more flexible > way to balance keeps with removals, but I don't know if I'll get to > implement them before Squeeze (after all, the freeze is next month). It > might be simpler to just change the defaults to the settings I gave > above, so that upgrading to Squeeze works as expected. Sounds great, I hope it's a fun project :) Thanks for the workaround! Drew -- To UNSUBSCRIBE, email to [email protected] with a subject of "unsubscribe". Trouble? Contact [email protected]
