Alex Miller <[email protected]> writes: > If not, why not?
It was originally caused by a bug in dh_strip_nondeterminism which is part of Debian's work toward reproducible builds (https://wiki.debian.org/ReproducibleBuilds). Of course it'll be much better if/when projects are just reproducible upstream as a matter of course, but my understanding is that's still quite a way off. > I think it's almost certainly this issue with clj / class timestamps. > afaik, nothing was ever filed about this in the Clojure ticket system. Makes sense -- It wasn't a Clojure issue. The debhelper bug was fixed, and still apears to be, at least with respect to Debian's 1.8 package: $ dpkg --status clojure1.8 | grep Version Version: 1.8.0-8 $ time clojure1.8 -e '' real 0m0.537s user 0m1.088s sys 0m0.060s Offhand I'd guess that either there's just some new issue, or perhaps there are jars that were built with the older version of dh_strip_notdeterminism lingering and getting in the way somehow. For what it's worth, I think the fix did something to make it so that the class timestamps would be at least a second newer than the clj timestamps (while still deterministic), and if I recall correctly, Chris Lamb came up with the fix. Thanks -- Rob Browning rlb @defaultvalue.org and @debian.org GPG as of 2011-07-10 E6A9 DA3C C9FD 1FF8 C676 D2C4 C0F0 39E9 ED1B 597A GPG as of 2002-11-03 14DD 432F AE39 534D B592 F9A0 25C8 D377 8C7E 73A4 _______________________________________________ Pkg-clojure-maintainers mailing list [email protected] https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/pkg-clojure-maintainers
