
Loading…
[work in progress] Reproducible builds #521
+32
−14
fwalch
commented
julianxhokaxhiu
commented
Maybe http://pivotallabs.com/barriers-deterministic-reproducible-zip-files/ will help you.
Also this could be helpful: http://stackoverflow.com/questions/19523063/zip-utility-giving-me-different-md5sum-every-time-in-linux (practically you should use the -X argument to discard special meta data information)
fwalch
commented
Thanks, but I think I'm already doing all of that. Debian has some strip-nondeterminism scripts, maybe that would help (didn't check them out yet).
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
This page is out of date. Refresh to see the latest.
Showing
with
32 additions
and 14 deletions.
- +3 −3 .travis.yml
- +15 −6 tools/make-chromium.sh
- +14 −5 tools/make-firefox.sh
6
.travis.yml
21
tools/make-chromium.sh
19
tools/make-firefox.sh
I noticed you had SHA1 sums on the build release page. With #496, you cannot really verify this hash locally, only get it from Travis:
I tried to create reproducible builds, i.e. the ZIPs generated by Travis are exactly the same as the ones generated locally. With this blog post, I got pretty far, but something's still off:
(partial diff)
So while all the headers and contents of the ZIPs are equal, the end of central directory records don't match. I'll see if that can be fixed as well.