Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

the opam debian package is not reproducible #3562

Closed
hannesm opened this issue Sep 26, 2018 · 2 comments
Closed

the opam debian package is not reproducible #3562

hannesm opened this issue Sep 26, 2018 · 2 comments

Comments

@hannesm
Copy link
Member

hannesm commented Sep 26, 2018

someone brought to my attention that opam2, now in buster, is not entirely reproducible. the very kind people from the reproducible builds project host a website containing their results: https://tests.reproducible-builds.org/debian/rb-pkg/buster/amd64/diffoscope-results/opam.html

what do we see there? the (optional) opam-docs package, which installs the doc/dev-manual (still at version 1.1.2 AFAICT), does contain - as common in latex - a timestamp of when the tex was translated to a pdf.

I think this can easily be avoided by using some waternarking (%%VERSION%%) in the tex - or unset \date{}. The timestamp of when latex was run is not very informative, it is much more interesting which opam release this document is targeting, or the git head!?

I haven't looked inside the dev-manual at all, but if it is specific for opam1, maybe it could be deleted or needs to be updated.

@h01ger
Copy link

h01ger commented Sep 26, 2018

thanks Hannes for reporting this.

If you want a timestamp in the manual, I suggest to use the last modification of the source code (and not the build time...), see https://reproducible-builds.org/specs/source-date-epoch/

@rjbou
Copy link
Collaborator

rjbou commented Oct 10, 2018

PR #3583 that remove dev manual merged.
Thanks for reporting!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants