[Aptitude-devel] Bug#762932: aptitude Bug#762932: With Aptitude::ProblemResolver::SolutionCost=removals, aptitude full-upgrade chooses to downgrade a package

Vincent Lefevre vincent at vinc17.net
Tue Apr 5 15:49:19 UTC 2016

On 2016-04-05 16:19:27 +0100, Manuel A. Fernandez Montecelo wrote:
> 2016-04-05 15:51 GMT+01:00 Vincent Lefevre <vincent at vinc17.net>:
> > What's the problem with offering this choice to the user?
> The problem is that I have to spend time implementing this request, and that:
> a) I think that there are many other things worth spending my time
> (even within the realm of aptitude) rather than implement this
> feature, and
> b) it means complicating even more the situation and complexity of
> with aptitude's resolver, which I feel that it's unhelpful in general

Well, from the user point of view, a downgrade is symmetrical
to an upgrade. So, if the aptitude dependency resolver is able
to count upgrades, I thought that this was as easy to count
downgrades (which would be sufficient to solve the problem).
So, I'm very surprised that this isn't the case.

Vincent Lefèvre <vincent at vinc17.net> - Web: <https://www.vinc17.net/>
100% accessible validated (X)HTML - Blog: <https://www.vinc17.net/blog/>
Work: CR INRIA - computer arithmetic / AriC project (LIP, ENS-Lyon)

More information about the Aptitude-devel mailing list