package libmupen64plus2 1.99.5-6 failed to install/upgrade: trying to overwrite shared '/usr/share/doc/libmupen64plus2/changelog.Debian.gz', which is different from other instances of package libmupen64plus2:i386

[Sarah Coins]

I tried to play Nintendo 64 ROM files, I canceled a download in the middle, now my system repeatedly tells me and tries to fix it, but it can't.

ProblemType: Package
DistroRelease: Ubuntu 12.10
Package: libmupen64plus2 1.99.5-6
Uname: Linux 3.4.0 x86_64
ApportVersion: 2.6.1-0ubuntu12
Architecture: amd64
Date: Mon Sep 16 16:53:33 2013
DuplicateSignature: package:libmupen64plus2:1.99.5-6:trying to overwrite shared '/usr/share/doc/libmupen64plus2/changelog.Debian.gz', which is different from other instances of package libmupen64plus2:i386
ErrorMessage: trying to overwrite shared '/usr/share/doc/libmupen64plus2/changelog.Debian.gz', which is different from other instances of package libmupen64plus2:i386
InstallationDate: Installed on 2012-04-26 (508 days ago)
InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Release amd64 (20120425)
MarkForUpload: True
SourcePackage: mupen64plus-core
Title: package libmupen64plus2 1.99.5-6 failed to install/upgrade: trying to overwrite shared '/usr/share/doc/libmupen64plus2/changelog.Debian.gz', which is different from other instances of package libmupen64plus2:i386
UpgradeStatus: Upgraded to quantal on 2013-05-14 (125 days ago)

[Sven Eckelmann (sven-eckelmann)]

I've looked at http://packages.ubuntu.com/quantal/libmupen64plus2 and compared the changelogs. The i386 version has a symlink to mupen64plus-data and the amd64 one has the real changelog. This is not how the Debian package was made and therefore I would guess it is caused by the Ubuntu build system.

And I would also guess that you don't need libmupen64plus2:i386 because the other packages you are using are :amd64. So please try to remove libmupen64plus2:i386.

Maybe someone here knows who is responsible for the ubuntu build system and the multiarch implementation in Quantal, raring, saucy, .... and can subscribe them to this bug

[Sven Eckelmann (sven-eckelmann)]

Just found following things in the buildlogs:

amd64 https://launchpadlibrarian.net/145850380/buildlog_ubuntu-saucy-amd64.mupen64plus-core_2.0-2_UPLOADING.txt.gz

Searching for duplicated docs in dependency libmupen64plus2...
  symlinking changelog.Debian.gz in libmupen64plus2-dbg to file in libmupen64plus2
pkgstripfiles: PNG optimization for package libmupen64plus2-dbg took 0 s

i386 https://launchpadlibrarian.net/145850640/buildlog_ubuntu-saucy-i386.mupen64plus-core_2.0-2_UPLOADING.txt.gz

Searching for duplicated docs in dependency mupen64plus-data...
  symlinking changelog.Debian.gz in libmupen64plus2 to file in mupen64plus-data
pkgstripfiles: PNG optimization for package libmupen64plus2 took 0 s
dpkg-deb: warning: 'debian/libmupen64plus2/DEBIAN/control' contains user-defined field 'Original-Maintainer'
dpkg-deb: warning: ignoring 1 warning about the control file(s)

dpkg-deb: building package `libmupen64plus2' in `../libmupen64plus2_2.0-2_i386.deb'.
INFO: pkgstriptranslations version 118
pkgstriptranslations: processing libmupen64plus2-dbg (in debian/libmupen64plus2-dbg); do_strip: , oemstrip:
pkgmaintainermangler: Maintainer field overridden to "Ubuntu Developers <email address hidden>"
pkgstripfiles: processing control file: debian/libmupen64plus2-dbg/DEBIAN/control, package libmupen64plus2-dbg, directory debian/libmupen64plus2-dbg
.. removing usr/share/doc/libmupen64plus2-dbg/changelog.gz
Searching for duplicated docs in dependency libmupen64plus2...
  symlinking changelog.Debian.gz in libmupen64plus2-dbg to file in mupen64plus-data
pkgstripfiles: PNG optimization for package libmupen64plus2-dbg took 0 s

So it is definitely a Ubuntu specific bug which seems to be caused by pkgbinarymangler.

[Sven Eckelmann (sven-eckelmann)]

Dear pkgbinarymangler maintainers,

I just wanted to give you the hint that this is still a problem in saucy and was not fixed with pkgbinarymangler (107) in precise (or returned as a regression).

[Sven Eckelmann (sven-eckelmann)]

It still seems to be a problem in the current builds of "The Trusty Tahr"

[Sven Eckelmann (sven-eckelmann)]

Dear pkgbinarymangler maintainers,

this is still a problem in the builds for utopic.

[Launchpad Janitor (janitor)]

Status changed to 'Confirmed' because the bug affects multiple users.

[Sven Eckelmann (sven-eckelmann)]

If you compare https://launchpadlibrarian.net/178524405/buildlog_ubuntu-utopic-i386.mupen64plus-core_2.0-6_UPLOADING.txt.gz and https://launchpadlibrarian.net/178524404/buildlog_ubuntu-utopic-amd64.mupen64plus-core_2.0-6_UPLOADING.txt.gz than you can see that the i386 (the one with the wrong symlink) has an error:

grep: ../mupen64plus-data/DEBIAN/control: No such file or directory

If this grep wouldn't fail than it would be detected that it is an "all" dependency from a non-all package