* Michael Stapelberg <[email protected]>, 2014-09-29, 19:49:
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?
What you could do is to move the PDF to separate -doc package. That
would reduce size of the -dev package from 1M to 340K. (Admittedly 1M is
not THAT big, so maybe it'd be overkill.)
For now, I’ll upload 1.17-6 soon, and then the file will be the same on
all architectures again.
Unfortunately, this upload didn't fix the problem for some reason. Now
the MD5 sums are:
6499c811b72bd3e21dcbd5bcd7f7c934 on arm64, mips;
10e5c01c6c99ea4e45f7b480b232727d elsewhere.
--
Jakub Wilk
--
To UNSUBSCRIBE, email to [email protected]
with a subject of "unsubscribe". Trouble? Contact [email protected]
