[Aptitude-devel] Bug#815551: aptitude: safe-upgrade removes manually installed package if dependency is on hold

Manuel A. Fernandez Montecelo manuel.montezelo at gmail.com
Mon Feb 29 21:35:44 GMT 2016

Control: tags -1 + pending

Hi Sven,

2016-02-28 02:21 To Sven Joachim:
>2016-02-28 1:47 GMT+00:00 Manuel A. Fernandez Montecelo
><manuel.montezelo at gmail.com>:
>> 2016-02-27 20:46 GMT+00:00 Sven Joachim <svenjoac at gmx.de>:
>>> That package has a reverse dependency which is also held back, and I can
>>> see that it has been marked as auto-installed as well, which is not
>>> surprising (anymore).
>> The commit above might be doing the wrong thing, but it doesn't have
>> much to do with holds but with marking the packages to "keep", for
>> example when one selects "Keep packages at current version" in the
>> interactive resolver.
>> It doesn't mark them unconditionally as automatic either, it tries to
>> force the Automatic parameter that was decided elsewhere (presumably,
>> determined to be the previous state before the current set of
>> decisions / pending actions was taken).
>BTW, I think that I've got a fix for this, but only if you got to this
>situation by selecting "Keep packages at current version" in the
>resolver (interactive or not).

So I am still not sure about the relationship between that commit and
the events as described in the original message.

But I am going to release a new version which addresses problems caused
indirectly by that commit (was marking all packages as "keep" as auto,
because of a wrong variable set elsewhere).  So if this was indeed the
cause of the problem that you experience, this should fix it.

If this doesn't fix it please reopen, and I will look into the issue
with more calm.

Manuel A. Fernandez Montecelo <manuel.montezelo at gmail.com>

More information about the Aptitude-devel mailing list