I guess that invalidation of the bug comes after the long time elapsed since its initial reporting and the subsequent inactivity.
Since reporting, I have simply stopped using aptitude, moving to apt- get, so I do not have any test case, nor I know if the bug is still valid. However, I wonder if before declaring the bug invalid, the logic in aptitude has been evaluated with respect to the possibility of something changing behind his back in the installed packages due to the usage of another package manager. If aptitude only relies on its own view of the installed packages (which might not reflect the actual situation of the installed packages due to the use of another package manager between two aptitude invocations) then its usage can become dangerous and IMHO the users should at least be warned about it. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/503765 Title: aptitude pkgstates gets corrupted To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/aptitude/+bug/503765/+subscriptions -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
