Control: reopen -1 1:5.18.16-5 Control: tags -1 - patch On 2025-05-07 Helmut Grohne <hel...@subdivi.de> wrote: > Package: libopts25-dev > Version: 1:5.18.16-5+b2 > Severity: serious > Justification: unpack error > User: debian...@lists.debian.org > Usertags: fileconflict > User: debian-cr...@lists.debian.org > Usertags: ftcbfs > Control: affects -1 + src:complexity
> Hi, > libopts25-dev explicitly declares that it is suitable for > coinstallation via Multi-Arch: same. Actually attempting to do so > results in an unpack error: > Unpacking libopts25-dev:s390x (1:5.18.16-5+b2) ... > dpkg: error processing archive > /tmp/apt-dpkg-install-959jVb/81-libopts25-dev_1%3a5.18.16-5+b2_s390x.deb > (--unpack): > trying to overwrite shared '/usr/share/man/man3/ao_string_tokenize.3.gz', > which is different from other instances of package libopts25-dev:s390x > According to the multiarch hinter, it is 40 affected files all residing > below /usr/share/man/man3/. Presumably, the manual pages are not > reproducible. I gave the mentioned manual page a look and the date in > the very first line of the manual page differs. [...] Hello, They are reproducible, the respective date is set to SOURCE_DATE_EPOCH using /usr/share/dpkg/pkg-info.mk. However a binNMU adds a changelog entry and therefore changes SOURCE_DATE_EPOCH. I am going to try to use find -maxdepth 1 -type f -name configure.ac -printf '%T@' | sed -e 's/\..*//' SOURCE_DATE_EPOCH as a workaround. cu Andreas -- `What a good friend you are to him, Dr. Maturin. His other friends are so grateful to you.' `I sew his ears on from time to time, sure'
