[Aptitude-devel] Bug#642030: aptitude: cannot forbid more than 1 version of a package

Vincent Lefevre vincent at vinc17.net
Thu Nov 12 13:37:40 UTC 2015

Control: reopen -1

On 2015-11-12 11:59:15 +0000, Manuel A. Fernandez Montecelo wrote:
> Even if this worked for multiple versions, if you are unsure in which
> version the package is going to fix a problem,

I am sure concerning which version*s* to forbid.

> it is more practical to use the Hold feature until you verify that
> it is fixed and safe to install, rather than to keep adding F
> versions every time that a new version pops up in the repositories
> (or failing to do so and be installed to a version that you don't
> want).

I want to be able to upgrade to future versions (actually be aware
of them, which is what "F" does). So, "Hold" is not OK here.

Remember that users can track both testing and unstable, and aptitude
does not always try to install the latest version. The problem I had
is that when I did "F" on the unstable version, aptitude then wanted
to upgrade to the testing version (i.e. en earlier version), which is

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