[Aptitude-devel] Bug#867226: aptitude seems dependency problems when there are none

Nikolaus Rath Nikolaus at rath.org
Sun Aug 6 07:38:44 UTC 2017

On Aug 05 2017, "Manuel A. Fernandez Montecelo" <manuel.montezelo at gmail.com> wrote:
> Hi,
> 2017-07-04 23:24 Nikolaus Rath:
>>However, according to aptitude, there is something seriously wrong:
>>$ aptitude
>># Select Actions -> Cancel pending actions
> Note that the behaviour of this changed in the last few versions, 0.8
> series I think, and that it doesn't cancel actions saved in previous
> sessions.

Ah, that explains it. Thanks!

>>This is annoying, because I would like to use aptitude to perform
>>some actions - yet there is no way to do so without making lots
>>of other changes to my system.
> Looks to me that there are actions saved from previous sessions (e.g. an
> upgrade of some packages, or request to install some new ones), and then
> got stuck due to problems of interdependencies between packages
> (e.g. the backports not able to link with some of the libraries; or
> clang-3.5 from unstable not being compatible with libraries that need to
> be installed).
> If you still haven't found a solution by now, or in future situations,
> you might want to try "aptitude keep-all" in the command line, or ":" in
> the root of the trees in the UI, and then perform the actions that you
> intended.

keep-all fixed the issues, thanks!

> Other than that, I cannot see any indication that aptitude gets confused
> with dependency problems per se, so I am not sure what you mean with the
> title of the bug report, can you please clarify?

I was assuming that the interactive "Cancel pending" was equivalent to
the CLI "keep-all". Since aptitude was still complaining about broken
dependencies afterwards, I assumed that it must be very confused about


GPG Fingerprint: ED31 791B 2C5C 1613 AF38 8B8A D113 FCAC 3C4E 599F

             »Time flies like an arrow, fruit flies like a Banana.«

More information about the Aptitude-devel mailing list