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
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.
Just found following things in the buildlogs:
amd64 https:/ /launchpadlibra rian.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:/ /launchpadlibra rian.net/ 145850640/ buildlog_ ubuntu- saucy-i386. mupen64plus- core_2. 0-2_UPLOADING. txt.gz
Searching for duplicated docs in dependency mupen64plus-data... libmupen64plus2 /DEBIAN/ control' contains user-defined field 'Original- Maintainer'
symlinking changelog.Debian.gz in libmupen64plus2 to file in mupen64plus-data
pkgstripfiles: PNG optimization for package libmupen64plus2 took 0 s
dpkg-deb: warning: 'debian/
dpkg-deb: warning: ignoring 1 warning about the control file(s)
dpkg-deb: building package `libmupen64plus2' in `../libmupen64p lus2_2. 0-2_i386. deb'. tions version 118 tions: processing libmupen64plus2-dbg (in debian/ libmupen64plus2 -dbg); do_strip: , oemstrip: ngler: Maintainer field overridden to "Ubuntu Developers <email address hidden>" libmupen64plus2 -dbg/DEBIAN/ control, package libmupen64plus2 -dbg, directory debian/ libmupen64plus2 -dbg doc/libmupen64p lus2-dbg/ changelog. gz
INFO: pkgstriptransla
pkgstriptransla
pkgmaintainerma
pkgstripfiles: processing control file: debian/
.. removing usr/share/
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.