[Aptitude-devel] Bug#570377: Bug#570377: aptitude chooses to remove packages instead of upgrading

Vincent Lefevre vincent at vinc17.net
Tue Feb 4 02:24:16 UTC 2014

On 2014-02-04 01:29:30 +0800, Daniel Hartwig wrote:
> There is nothing fundamentally better or worse about either removals
> or installs, in some situations you might find this:
>  solution 1: upgrade 20 packages
>  solution 2: remove 1
> Whichever is more preferable in these situations is up to the
> individual user to decide based on whatever particular packages are
> suggested for upgrade, install, or removal—aptitude can not know how
> the user values those individual actions.

Could you explain why, e.g. by giving a practical example?

Because I would say: A remove can be caused by some obsolete package
due to a conflict with the newly installed package (or one of its
dependencies). But in such a case, the remove would occur in *every*
solution. If a package is not obsolete, aptitude should never propose
it for removal when another solution can solve the problem.

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