Hey Jakub, On Mon, Sep 15, 2014 at 9:54 AM, Jakub Wilk <jw...@debian.org> wrote: > Package: libtomcrypt-dev > Version: 1.17-5 > User: multiarch-de...@lists.alioth.debian.org > Usertags: multiarch > > libtomcrypt-dev is marked as "Multi-Arch: same", but the following file is > architecture-dependent: > > /usr/share/doc/libtomcrypt-dev/crypt.pdf.gz > > MD5 sums of the file are: > > 6499c811b72bd3e21dcbd5bcd7f7c934 on arm64 and ppc64el; > 150c0017b77e05d325dda105716569ad elsewhere. The difference is not caused by the architecture, but by the version of Build-Dependencies with which the file was compiled — on arm64 and ppc64el it was built last month, presumably because those are new architectures, and it was built using TeXLive 2014. On the other (older) architectures, the package was built 270 days ago, with TeXLive 2013.
I don’t think Debian offers a way to have reproducible builds under these circumstances, i.e. I cannot expect all builds of my package to have _exactly_ the same Build-Dependencies available. Hence, I’m inclined to close this bug report without actually doing anything. Do you agree or is there something that we can do to avoid getting into this situation in the future? For now, I’ll upload 1.17-6 soon, and then the file will be the same on all architectures again. -- Best regards, Michael -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
