Bug#836596: libavutil55: borked NMUs with differing changelog

[Thorsten Glaser]

Package: libavutil55
Version: 7:3.1.3-1+b3
Severity: normal

[…]
Unpacking dput (0.10.3) over (0.9.6.4) ...
Preparing to unpack .../08-libavutil55_7%3a3.1.3-1+b3_i386.deb ...
De-configuring libavutil55:x32 (7:3.1.3-1) ...
Unpacking libavutil55:i386 (7:3.1.3-1+b3) over (7:3.1.3-1) ...
Preparing to unpack .../09-libavutil55_7%3a3.1.3-1+b3_x32.deb ...
Unpacking libavutil55:x32 (7:3.1.3-1+b3) over (7:3.1.3-1) ...
dpkg: error processing archive /tmp/apt-dpkg-install-rPYNV8/09-libavutil55_7%3a3.1.3-1+b3_x32.deb (--unpack):
 trying to overwrite shared '/usr/share/doc/libavutil55/changelog.Debian.gz', which is different from other instances of package libavutil55:x32
Preparing to unpack .../10-libswresample2_7%3a3.1.3-1+b3_i386.deb ...
De-configuring libswresample2:x32 (7:3.1.3-1) ...
[…]

And indeed, the file differs:

-rw-r--r--  1 tglase tglase  7526 Aug 28 12:12 clog-i386.gz
-rw-r--r--  1 tglase tglase  7642 Sep  3 16:36 clog-x32.gz

On x32, the binNMU was applied directly, apparently:

tglase at tglase:~ $ diff -u clog-*
--- clog-i386   2016-08-28 12:12:00.000000000 +0200
+++ clog-x32    2016-09-03 16:36:00.000000000 +0200
@@ -1,3 +1,10 @@
+ffmpeg (7:3.1.3-1+b3) unstable; urgency=medium
+
+  * Binary-only NMU: Rebuild against against libchromaprint1.
+  * Manually built to resolve circular Build-Depends with chromaprint.
+
+ -- x32 Build Daemon (frobozz) <buildd_x32-frobozz at buildd.debian-ports.org>  Sat, 03 Sep 2016 07:36:24 -0700
+
 ffmpeg (7:3.1.3-1) unstable; urgency=medium

   * Team upload.

I’ll Cc the relevant people for that.

-- System Information:
Debian Release: stretch/sid
  APT prefers unreleased
  APT policy: (500, 'unreleased'), (500, 'buildd-unstable'), (500, 'unstable')
Architecture: x32 (x86_64)
Foreign Architectures: i386, amd64

Kernel: Linux 4.6.0-1-amd64 (SMP w/4 CPU cores)
Locale: LANG=C, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/lksh
Init: sysvinit (via /sbin/init)