Am 20.10.2016 um 01:03 schrieb Axel Beckert: > Hi Michael, > > Michael Biebl wrote: >> Am 20.10.2016 um 00:44 schrieb Michael Biebl: >>> So, the complete steps to reproduce the issue: >>> - create a fresh chroot via debootstrap >>> - start aptitude in interactive mode, select a random, non-related >>> package, say netbase, mark it as auto-installed via "M"
fwiw, this step can be replaced by $ aptitude markauto netbase or actually any other aptitude action which creates /var/lib/aptitude/pkgstates, like installing a package via aptitude. >> At this point, you should have /var/lib/aptitude/pkgstates >> >>> - exit aptitude and install the example deb via apt install ./... >>> - then check the auto state of gobject-introspection. It will now differ >>> between aptitude and apt. >>> >>> The key here is, that you need to have a /var/lib/aptitude/pkgstates >> >> Removing that file again: >> >> $ aptitude show gobject-introspection | grep Auto >> Automatically installed: yes >> >> Once the pkgstates file exists, aptitude seems to no longer read the >> autobit state from apt. > > Thanks for all these details! Seems as if there are still some corner > cases where aptitude doesn't sync the autoinstalled bit properly -- > changing an autoinstalled bit manually without any install/remove > action seems to such a case according to your description. Afaics, once /var/lib/aptitude/pkgstates exists, which it will after any non-trivial use of aptitude, the sync between apt and aptitude is completely broken. So I suspect basically everyone will be affected by this, who uses both apt and aptitude. I wouldn't call that a corner case. But maybe I'm just a bit weird that I use both apt and aptitude at the same time :-) Regards, Michael -- Why is it that all of the instruments seeking intelligent life in the universe are pointed away from Earth?
signature.asc
Description: OpenPGP digital signature