Re: aptitude weirdness wrt upgrades and keeps
* Miles Bader <firstname.lastname@example.org> [111014 03:04]:
> Paul Wise <email@example.com> writes:
> >> Not a solution for the interactive mode, or am I wrong?
> > Not AFAICT, I only read the documentation rather than the code though.
> Kinda surprising, actually; this has long been the #1 most horrible
> thing about aptitude, and one about which there's been plenty of
> [With the normal "U" command, for my typical usage, aptitude seems to
> choose the worst possible solution about 98% of the time.]
You can use "aptitude safe-upgrade --visual-preview", though this is not
particularly convenient when already running the aptitude cua.
You can also check out "Aptitude::Always-Use-Safe-Resolver".
I, too, find that the priorities given to the resolver's solutions and
the action I intended are often quite disparate. The above remedies can
be helpful, but are not real solutions.