Hello all, just dropping some notes here after having looked into this a bit.
On Fri, Aug 15, 2025 at 12:47:57PM +0000, NN 708 wrote: > When attempting to install both AMD64 and ARM64 architectures of > libpsl-dev simultaneously, the installation fails due to conflicting > '/usr/share/man/man3/libpsl.3.gz' files. > [...] > dpkg: error processing archive > /tmp/apt-dpkg-install-Gma12Z/10-libpsl-dev_0.21.2-1.1+b1_arm64.deb (--unpack): > trying to overwrite shared '/usr/share/man/man3/libpsl.3.gz', which is > different from other instances of package libpsl-dev:arm64 > [...] That manpage contains a date string derived during build from the latest Debian changelog entry. But when the package is binNMU'd, this binNMU's changelog date is used instead, and that date might then differ depending on when the architecture-specific binNMU actually occurred, which might or all too easily might not be on the same date, making the resulting packages potentially fail to be co-installed as seen above. For reference, as such the 0.21.2-1.1 packages were still co-installable, whereas the +b1 and the +b2 were not anymore. I am unsure how to best tackle this issue. It would be possible to override SOURCE_DATE_EPOCH during build, ignoring any binNMU datestamps, but that seems error-prone and invasive. On the other hand, sbuild already supports --binNMU-timestamp, but I don't know whether it can be relied upon to be set during each binNMU. So, no solution as of yet, but I will keep checking. Cheers, Flo
signature.asc
Description: PGP signature
