[DRE-maint] Bug#912857: libruby2.5 is wrongly marked Multi-Arch: same

Antonio Terceiro terceiro at debian.org
Thu Nov 29 19:52:16 GMT 2018

Control: done -1 2.5.3-3

On Sun, Nov 04, 2018 at 05:18:24PM +0100, Helmut Grohne wrote:
> Package: libruby2.5
> Version: 2.5.1-6+b1
> Severity: important
> User: helmutg at debian.org
> Usertags: rebootstrap
> libruby2.5 is wrongly marked Multi-Arch: same. It fails to coinstall on
> amd64 and arm64:
> | Unpacking libruby2.5:arm64 (2.5.1-6+b1) ...
> | dpkg: error processing archive /tmp/apt-dpkg-install-xsTPRC/29-libruby2.5_2.5.1-6+b1_arm64.deb (--unpack):
> |  trying to overwrite shared '/usr/lib/ruby/2.5.0/rdoc/generator/template/darkfish/images/macFFBgHack.png', which is different from other instances of package libruby2.5:arm64
> | dpkg-deb: error: paste subprocess was killed by signal (Broken pipe)
> | Errors were encountered while processing:
> |  /tmp/apt-dpkg-install-xsTPRC/29-libruby2.5_2.5.1-6+b1_arm64.deb
> | E: Sub-process /usr/bin/dpkg returned an error code (1)
> The multiarch hinter says:
> | libruby2.5 conflicts on /usr/lib/ruby/2.5.0/rdoc/generator/template/darkfish/images/macFFBgHack.png on any two of amd64, arm64, armel, armhf, and 6 more
> Please remove the erroneous Multi-Arch: same marking or fix the file
> conflict.

It seems the final form of that file was capturing the build timestamp,
but that seems to not be the case anymore.  I checked this again against
libruby2.5 2.5.3-3 from the archive and a local binNMU-style build done
with sbuild, and the files are identical. I also tested installing
libruby2.5:i386 and libruby2.5:arm64 from the archive on an amd64
container, and it went fine.
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 833 bytes
Desc: not available
URL: <http://alioth-lists.debian.net/pipermail/pkg-ruby-extras-maintainers/attachments/20181129/23203f33/attachment.sig>

More information about the Pkg-ruby-extras-maintainers mailing list