Comment 2 for bug 1075366

On Tue, Nov 06, 2012 at 02:03:50AM -0000, Daniel Hartwig wrote:
> On 6 November 2012 08:31, Steve Langasek <email address hidden> 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);

Have never used aptitude on this system.

> - upgrading packages with python-aptdaemon (e.g. via
> software-center). [2]

I use update-manager for my upgrades, not software-center. Does the same
issue apply?

I think a lot of my issue probably comes to the way I reinstalled my system
to a new hard drive, using dpkg --get-selections rather than apt-clone. But
that doesn't explain it for any libraries that were installed after my
machine's brain-swap.