On Tue, Jan 20, 2026 at 09:40:45PM +0100, Michal Politowski wrote: > Package: librecode3 > Version: 3.7.15-1+b1 > Severity: important > > Preparing to unpack .../librecode3_3.7.15-1+b1_i386.deb ... > Unpacking librecode3:i386 (3.7.15-1+b1) over (3.7.15-1) ... > dpkg: error processing archive > /var/cache/apt/archives/librecode3_3.7.15-1+b1_i386.deb (--unpack): > trying to overwrite shared '/usr/share/doc/librecode3/changelog.Debian.gz', > which is different from other instances of package librecode3:i386 > Errors were encountered while processing: > /var/cache/apt/archives/librecode3_3.7.15-1+b1_i386.deb
Thanks for the report. I finally understand the information in tracker.debian.org about recode when it says this: " There are issues with the multiarch metadata for this package. librecode3 conflicts on /usr/share/doc/librecode3/changelog.Debian.gz on any two of amd64, arm64, armhf, i386, and 3 more The diffoscope program shows these differences between amd64 and i386: │ │ │ │ recode (3.7.15-1+b1) sid; urgency=low, binary-only=yes │ │ │ │ │ │ │ │ - * Binary-only non-maintainer upload for amd64; no source changes. │ │ │ │ + * Binary-only non-maintainer upload for i386; no source changes. │ │ │ │ * Rebuild to enable GCS on arm64 │ │ │ │ │ │ │ │ - -- all / amd64 / i386 Build Daemon (x86-grnet-03) <[email protected]> Sat, 17 Jan 2026 09:09:49 +0000 │ │ │ │ + -- all / amd64 / i386 Build Daemon (x86-conova-02) <[email protected]> Sat, 17 Jan 2026 17:13:40 +0000 Should I really change "Multi-Arch: same" to "Multi-Arch: no" as suggested by the multi-arch hinter, or maybe we should change the way we do binNMUs? (or maybe I can just make another upload so that all archs are in sync again?) I'm confused because this seems to me the kind of issue that a normal maintainer should not worry about. (I'm Cc:ing Helmut Grohne for help). Thanks.
