On Thu, Mar 13, 2025 at 11:15:47AM +0100, Helmut Grohne wrote: > Package: libcompress-raw-bzip2-perl > Version: 2.213-1+b1 > Severity: serious > User: debian...@lists.debian.org > Usertags: fileconflict > Tags: patch > > libcompress-raw-bzip2-perl is marked Multi-Arch: same, but > /usr/share/man/man3/Compress::Raw::Bzip2.3pm.gz actually differs between > amd64/arm64/i386 and armel/armhf/mips64el/ppc64el/s390x. As a result > unpacking multiple instances fails:
[...] > On the flip side, using Multi-Arch: same doesn't practically work, > because it depends on perl-base, which is not coinstallable. As a > result, I recommend dropping it. For the record, I believe the difference in the manual pages is because they embed a date stamp based on $SOURCE_DATE_EPOCH, which for binNMUs gets set to the time of each build separately (because they append an entry to debian/changelog at build time.) This and the other recent case (libalgorithm-diff-xs-perl / #1100547) both happened to get their binNMUs scheduled around midnight, so the quicker ones got a different build date. https://sources.debian.org/src/perl/5.40.1-2/cpan/podlators/lib/Pod/Man.pm/#L994 I suspect that the best fix (short of replacing the whole binNMU concept with automated sourceful uploads) would be to remove the date from the generated manual pages altogether. That said, I'm not really keen on revisiting this stuff, at least until it causes actual problems. -- Niko Tyni nt...@debian.org
