Bug#774889: removed packages not even part stable.... who's the maintainer?!

[Andreas Beckmann]

On 2015-02-10 23:57, Andreas Beckmann wrote:
> OK, there are only less than 40 logfiles mentioning gdm, I'll check in
> how many cases gdm survives the upgrade from squeeze to wheezy (or
> jessie). A significant fraction is obsolete packages.

The good thing is, gdm/squeeze won't survive the upgrade to jessie:

  Investigating (0) libaudit-common [ amd64 ] < none -> 1:2.4-1 > ( libs )
  Broken libaudit-common:amd64 Breaks on libaudit0 [ amd64 ] < 1:1.7.18-1.1 > ( libs )
    Considering libaudit0:amd64 0 as a solution to libaudit-common:amd64 9
    Added libaudit0:amd64 to the remove list
    Fixing libaudit-common:amd64 via remove of libaudit0:amd64
  Investigating (0) gdm [ amd64 ] < 2.20.11-4 > ( gnome )
  Broken gdm:amd64 Depends on libaudit0 [ amd64 ] < 1:1.7.18-1.1 > ( libs )
    Considering libaudit0:amd64 0 as a solution to gdm:amd64 -1
    Removing gdm:amd64 rather than change libaudit0:amd64

This would have happened in the failing upgrade scenario as well:

  The following packages will be REMOVED:
    gdm libaudit0 libcogl-pango0 libcogl9 libebook-1.2-13 libebook1.2-9
    libecal1.2-7 libedataserverui-3.0-1 libedataserverui1.2-8 libgjs0b
    libgnome-desktop-3-2 libjpeg62 libmetacity-private0a libmutter0 obexd-client

Just the unpack ordering chosen by apt was unlucky.
If you could add back
  Conflicts+Replaces: gdm
to gdm3 for one more stable release (jessie), the gdm saga could be closed
eventually.


Andreas