[Aptitude-devel] Bug#782777: aptitude: marks certain packages as "new" and "not auto-installed" on every start of aptitude

[Axel Beckert]

Hi again,

Axel Beckert wrote:
> > Since the last upgrade of apt (1.0.9.7 -> 1.0.9.8) the following happens
> > reproducably in aptitude every time it's started:

Actually that's seems a coincidence.

I've just downgraded all packages built from the apt source package
(except apt-doc :-) to 1.0.9.7 from testing and this behaviour persists:

> > The packages below are displayed as "new" (even if I forget all new packages
> > then) and as not auto-installed (even if I mark them again to be).
> > 
> > Next start, and it's again like below (without and update in the meantime)
> > 
> > --\ New Packages (13)
> >   --\ debug - Debugging symbols (11)
> >     --\ main - The main Debian archive (11)
> > i     libasan1-dbg                                 4.9.2-10       4.9.2-10
> > i     libatomic1-dbg                               4.9.2-10       4.9.2-10
> > i     libcilkrts5-dbg                              4.9.2-10       4.9.2-10
> > i     libgcc1-dbg                                  1:4.9.2-10     1:4.9.2-10
> > p     libgfortran3-dbg                             <none>         4.9.2-10
> > i     libgomp1-dbg                                 4.9.2-10       4.9.2-10
> > i     libitm1-dbg                                  4.9.2-10       4.9.2-10
> > i     liblsan0-dbg                                 4.9.2-10       4.9.2-10
> > i     libstdc++6-4.9-dbg                           4.9.2-10       4.9.2-10
> > i     libtsan0-dbg                                 4.9.2-10       4.9.2-10
> > i     libubsan0-dbg                                4.9.2-10       4.9.2-10
> >   --\ libdevel - Development files for libraries (2)
> >     --\ main - The main Debian archive (2)
> > i     libgcc-4.9-dev                               4.9.2-10       4.9.2-10
> > p     libgfortran-4.9-dev                          <none>         4.9.2-10

It is interesting all these packages are built from the same source
package (gcc-4.9), but not all of the packages built from that source
package are affected -- especially gcc-4.9 itself is not affected.

But gcc-4.9/4.9.2-10 was uploaded already in December 2014. So that
upload is surely not the trigger.

But gcc-4.9/4.9.2-12 has been uploaded to experimental on the same day
as apt/1.0.9.8, so the observation that it happens since the
apt/1.0.9.8 upload is correct -- just not related.

But
http://metadata.ftp-master.debian.org/changelogs/main/g/gcc-4.9/experimental_changelog
doesn't show anything obvious related to packaging which could confuse
aptitude.

So no further idea what could have triggered this behaviour.

		Regards, Axel
-- 
 ,''`.  |  Axel Beckert <abe at debian.org>, http://people.debian.org/~abe/
: :' :  |  Debian Developer, ftp.ch.debian.org Admin
`. `'   |  4096R: 2517 B724 C5F6 CA99 5329  6E61 2FF9 CD59 6126 16B5
  `-    |  1024D: F067 EA27 26B9 C3FC 1486  202E C09E 1D89 9593 0EDE