[Aptitude-devel] Bug#663699: aptitude: always sets a package to "remove" which had been marked as "install"

[Manuel A. Fernandez Montecelo]

Control: tags -1 + moreinfo


Hi Johannes,

2012-03-13 12:47 Johannes Rohr:
>Package: aptitude
>Version: 0.6.5-1
>Severity: normal
>
>Dear Maintainer,
>
>the following has happened:
>
>I purged the package libsocialweb-client2 using dpkg --purge
>
>In aptitude I re-installed the package
>
>Next time I start aptitude, the package is again set to "remove" thus breaking gnome-control-center and the rest of GNOME
>
>I set the package to "install" again, and everything looks fine. I quit aptitude
>
>Next time I launch aptitude, the package is again set to "remove", even though this breaks other packages
>
>Again, I can manually set the package to "install" and everything looks fine again - until next time I launch aptitude
>
>and so on.
>
>What is fscked up here?

Can you reproduce this with newer versions?  I have never witnessed this
behaviour.

If you can still reproduce it (or remember the details), please tell us
what the bottom half of the window says when you select the given
package, the reason why aptitude shows the package as "broken" or wants
to remove it, if there is any.

Something like this (which happens in my system when trying to upgrade
python3-uno, but it's set as "broken" because of interdependencies with
libreoffice):

========================
Some dependencies of python3-uno are not satisfied:
* python3-uno depends on libreoffice-core (= 1:5.0.1-1)
========================

You can also cycle the contents of that window with 'i', in one of them
shows problematic (reverse) dependency relations related with the
current package:

========================
ih  libreoffice-calc   Depends    libreoffice-core (= 1:4.4.4-1)
ihA libreoffice-core   Depends    libreoffice-common (> 1:4.4.4)
ihA libreoffice-common Recommends python3-uno (>= 4.4.0~beta2)
========================


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