Ludovic Courtès <[email protected]> writes: > In particular, in Guix and Nix, timestamps on build artifacts are > reset to the Epoch + 1 second, for reproducibility purposes. This > means that .scm and .go files have the exact same timestamp.
Ahh, OK. Clojure had this same problem in Debian a good while back with dh_strip_nondeterminism. There it was causing performance problems because clojure would recompile all the packaged source code every time it ran, even though it also had compiled code, because the timestamps in the jar were equal and clojure did consider that "stale". I think it was fixed by having dh_strip_nondeterminism set the source time a bit before the compiled time while stripping. https://bugs.debian.org/877418 > Now, I would hope that the problem you describe is rare enough in > practice that this is not too much of a problem? Well, as mentioned in my reply to Nikolaos Chatzikonstantinou, I believe I've seen it a number of times, but not often, and it was quite confusing, which is why I started looking around in the first place. But also as mentioned, I did wonder if there might be some additional, more likely cause. Thanks for taking a look -- 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
