Comment 11 for bug 854622

I downloaded the i386 and amd64 binaries from that version from https://launchpad.net/ubuntu/+source/glib2.0/2.29.92-0ubuntu1/+build/2793297 and https://launchpad.net/ubuntu/+source/glib2.0/2.29.92-0ubuntu1/+build/2793299. They both have an identical changelog.Debian.gz, so I'm not sure where the changelog.Debian.gz with the 'apt-get changelog libglib2.0-data' came from in this particular instance. Also, both these two debs and libglib2.0-data's changelog.Debian.gz are proper files, not symlinks.

In theory, such a situation could arise like this:

 (1) The i386 build builds -0 and -data, both get identical changelog.Debian.gz, and the one from libglib2.0-0 gets symlinked to libglib2.0-data.

 (2) After that, libglib2.0-data's changelog gets truncated, and a pointer added to apt-get changelog.

 (3) The amd64 build doesn't build the arch:all libglib2.0-data, and thus libglib2.0-0:amd64's changelog.Debian.gz won't be a symlink. During truncation it would point to "apt-get changelog libglib2.0-0".

However, that can't be the case: pkgbinarymangler does not do symlinks from arch:any to arch:all for this very reason, rendering (1) impossible. Also, changelog stripping happens _first_, and symlinking afterwards, so the symlinking takes care only to symlink identical files, rendering (2) impossible. Thirdly, the packages built by launchpad all have changelog.Debian.gz as proper files, rendering (3) impossible.

In such a situation, could you please give me the output of

  ls -l /usr/share/doc/*glib2.0*/changelog.Debian.gz
  dpkg -S /usr/share/doc/*glib2.0*/changelog.Debian.gz

to see which changelog.Debian.gz gets claimed by which package, and which are symlinks? Michael, did you happen to get the glib packages from a different place than the archive, i. e. can you please give me the output of

  apt-cache policy libglib2.0-0

?