On 6 November 2012 08:31, Steve Langasek <steve.langa...@canonical.com> wrote: > FWIW, we seem to be doing a poor job in general of getting packages > correctly marked for autoremoval. On my desktop system: > > $ for pkg in $(apt-mark showmanual) ; do grep-status -FPackage -X $pkg -a > -FSection -X libs -sPackage; done | uniq | wc -l > 889 > $ > > I don't think those are all due to this particular bug, but I'm pretty > sure they're almost all wrong. :/
Potential sources of this: - upgrading packages with some combinations of aptitude (< 0.6.4-1) and apt (≥ 0.8.11.2); [1] - some other issues in current versions of aptitude (problem resolver; cancelling removal of packages); - upgrading packages with python-aptdaemon (e.g. via software-center). [2] These are just the cases that I am aware of. I have investigated some others (apt, python-apt) which seem to be ok, though python-apt conflates “FromUser=true” (pkgDepCache::MarkInstall et al.) with “mark this package manually installed” in mark_upgrade, which is not strictly true. If the system is a relatively fresh install, then it is easier to determine whether the issue is still present. [1] http://bugs.debian.org/432017#152 [2] http://bugs.debian.org/685044 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1075366 Title: Never-MarkAuto-Sections:: oldlibs gives wrong behavior To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1075366/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
