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

On 2016-04-05 16:19:27 +0100, Manuel A. Fernandez Montecelo wrote: > 2016-04-05 15:51 GMT+01:00 Vincent Lefevre : > > 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

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

2016-04-05 15:51 GMT+01:00 Vincent Lefevre : > 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

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

On 2016-04-05 15:26:38 +0100, Manuel A. Fernandez Montecelo wrote: > 2016-04-05 15:21 GMT+01:00 Vincent Lefevre : > > On 2016-04-05 13:42:49 +0100, Manuel A. Fernandez Montecelo wrote: > >> So after studying this for a while, this is normal behaviour when using > >> "removals",

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

On 2016-04-05 13:42:49 +0100, Manuel A. Fernandez Montecelo wrote: > So after studying this for a while, this is normal behaviour when using > "removals", which only pays attention to minimise the number of > removals, no matter any other considerations like upgrades, downgrades, > or prefering

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

2016-04-05 15:21 GMT+01:00 Vincent Lefevre : > On 2016-04-05 13:42:49 +0100, Manuel A. Fernandez Montecelo wrote: >> So after studying this for a while, this is normal behaviour when using >> "removals", which only pays attention to minimise the number of >> removals, no matter

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

Control: severity -1 wishlist Control: tags -1 + wontfix Hi, 2015-09-21 12:43 Manuel A. Fernandez Montecelo: If I ask aptitude to upgrade a package and the dependencies cannot be fulfilled (as explained above for unstable), it is natural that aptitude tries to come up with weird solutions.