On Sun, Dec 04, 2005 at 02:26:54PM +0100, Mikael Nilsson <[EMAIL PROTECTED]> was heard to say: > Package: aptitude > Version: 0.4.0-3 > Severity: normal > > > I'm generally quite happy with the new problem resolver in aptitude, but in > a few cases I find it less that useful. > > Case in point: I was trying to install evolution from experimental. aptitude > is your friend here, because this is a complex transition involving dbus and > a lot of gnome stuff. > > I did: > > aptitude -t experimental install evolution > > which I assumed would do the job for me. However, the first 20 or so > alternatives that it presented as a problem resolution involved either > removing evolution altogether, or not upgrading it. It was only after a > looong series of "no, no, no..." that it found a working solution. See > below. > > I find it a bit strange that it didn't find this earlier. After all, I asked > for an upgrade of evolution, so that should be priority #1. Removing it > should probably *never* be an option, nor keeping it. Or at least a last > resort... The first alternative to show should be "what happens if you > *really* want to do this?". Only when that turns out not to be possibly > should you consider the other options. > > Is there an apt.conf option that increases the penalty for those options? > Maybe the default value of that penalty should be considerably increased.
The option in question is Aptitude::ProblemResolver::PreserveManualScore; I would be interested in hearing whether you have any trouble with that cranked up to 1000 or so over a period of time. (the default is 60) I'm not terribly interested in adding more ways to throw away solutions entirely, as the more complicated you make those schemes, the more likely that they'll eliminate solutions that are actually good. For instance, saying "never remove packages that are to be upgraded" fails when you're upgrading two packages A and B, where the newer version of A conflicts with B. Daniel
signature.asc
Description: Digital signature
