[Aptitude-devel] Bug#566343: aptitude constantly switches between console-setup and console-setup-mini
Manuel A. Fernandez Montecelo
manuel.montezelo at gmail.com
Sun May 8 10:56:54 UTC 2016
Control: tags -1 - moreinfo
Control: close -1
2016-05-08 04:18 Russ Allbery:
>"Manuel A. Fernandez Montecelo" <manuel.montezelo at gmail.com> writes:
>> 2010-01-28 17:59 Daniel Burrows:
>
>>> I tracked down one bug that was part of this: aptitude was incorrectly
>>> treating the automatic removal as a "manual" action, so it was
>>> penalizing solutions that restore the package. However, in at least
>>> one of the two cases that's involved, it still tries to switch to the
>>> other console-setup package, because it solves more outstanding
>>> dependencies than the alternative, so it looks like a locally better
>>> solution. Probably an argument for tracking down those algorithms to
>>> split a constraint graph and work on it piecewise...
>>>
>>> I might wait a bit on rewiring the upgrade commands. It'll require
>>> a bunch of coding, and I suspect that it won't actually fix all the
>>> problems (there are probably cases where aptitude would get confused
>>> and start fixing dependencies of stuff that was going to be removed
>>> anyway). The real fix here is to integrate autoremoval into the
>>> dependency solver, so it knows exactly what the outcomes of its actions
>>> are.
>
>> Have you experienced this problem lately?
>
>I haven't. I've mostly switched over to using apt, and haven't run into
>any problems when I've used aptitude.
>
>It's fine to close this bug from my perspective if you think it's probably
>fixed.
I think it is fixed, because there I haven't seen similar complaints
with recent versions in the hundreds of bugs that I was reviewing /
triaging lately.
So closing now. Thanks for the feedback.
Cheers.
--
Manuel A. Fernandez Montecelo <manuel.montezelo at gmail.com>
More information about the Aptitude-devel
mailing list