[Aptitude-devel] Bug#867585: mention why there is no "unkeep"

積丹尼 Dan Jacobson jidanni at jidanni.org
Fri Jul 7 14:26:22 UTC 2017


Package: aptitude
Version: 0.8.8-1
Severity: wishlist
File: /usr/share/man/man8/aptitude-curses.8.gz

We read
           The difference between hold and keep is that hold will cause a
           package to be ignored by future safe-upgrade or full-upgrade
           commands, while keep merely cancels any scheduled actions on the
           package.  unhold will allow a package to be upgraded by future
           safe-upgrade or full-upgrade commands, without otherwise altering
           its state.

Perhaps add (if my hunch is correct):

The reason there is no "unkeep" command is that keep only affects the
computations done on the current command line (I, Dan Jacobson, only
know about the command line and do not use the curses version of
aptitude.) No state is changed in /var/lib/aptitude/pkgstates (my
guess.) Thus doing only
# aptitude keep somepackage
is a no-op(?, and really should trigger an error?)
Therefore keep is only useful in combinations with install and
full-upgrade, safe-upgrade, in its ":" suffix form (at least on the
command line.)

(The above are all my guesses.)



More information about the Aptitude-devel mailing list