Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > linux.debian.bugs.dist > #842629
| From | Russ Allbery <rra@debian.org> |
|---|---|
| Newsgroups | linux.debian.bugs.dist, linux.debian.policy |
| Subject | Bug#844431: Reproducibility in Policy |
| Date | 2017-08-12 03:10 +0200 |
| Message-ID | <udt69-2oB-3@gated-at.bofh.it> (permalink) |
| References | <sDPS9-7Wd-3@gated-at.bofh.it> <udrxo-1lO-21@gated-at.bofh.it> <sDPS9-7Wd-3@gated-at.bofh.it> <udrxo-1lO-21@gated-at.bofh.it> |
| Organization | The Eyrie |
Cross-posted to 2 groups.
Sean Whitton <spwhitton@spwhitton.name> writes: > ==== Proposal: ==== > This is what Holger and I think we should add to Policy, after > readability tweaks: > Packages should build reproducibly, which for purposes of this > document means that given > - a version of a source package unpacked at a given path; > - a set of versions of installed build-dependencies; and > - a build architecture, > repeatedly building the source package on the architecture with those > versions of the build dependencies installed will produce bit-for-bit > identical binary packages. I think we need to add all environment variables starting with DEB_* to the prerequisites. If you set DEB_BUILD_OPTIONS=nostrip or DEB_BUILD_MAINT_OPTIONS=hardening=all, you'll definitely get a different package, for instance. I feel like there are a bunch of other environment variables that have to be consistent, although I'm not sure how to specify that since other environment variables shouldn't matter. But, say, setting GNUTARGET is very likely to cause weirdness by changing how ld works. There are probably more interesting examples. How does the current reproducible build testing work with the environment? Maybe we should just document that for right now and relax it later if needed? > ==== Explanation: ==== > The definition from the reproducible builds group[1] says: > A build is reproducible if given the same source code, build > environment and build instructions, any party can recreate > bit-by-bit identical copies of all specified artifacts. > The relevant attributes of the build environment, the build > instructions and the source code as well as the expected > reproducible artifacts are defined by ... distributors. > i.e. Debian has to define the build environment, source code and build > instructions. I think that my wording defines these as Debian currently > understands them. > Later, we could narrow the definition of build environment by adding > more constraints, but we're not there yet. > [1] https://reproducible-builds.org/docs/definition/ We should add a link to that page (maybe in a footnote). -- Russ Allbery (rra@debian.org) <http://www.eyrie.org/~eagle/>
Back to linux.debian.bugs.dist | Previous | Next — Previous in thread | Next in thread | Find similar | Unroll thread
Bug#844431: Reproducibility in Policy Sean Whitton <spwhitton@spwhitton.name> - 2017-08-12 01:30 +0200
Bug#844431: Reproducibility in Policy Chris Lamb <lamby@debian.org> - 2017-08-12 02:40 +0200
Bug#844431: Reproducibility in Policy Russ Allbery <rra@debian.org> - 2017-08-12 03:10 +0200
Bug#844431: Reproducibility in Policy Johannes Schauer <josch@debian.org> - 2017-08-12 10:40 +0200
Bug#844431: Reproducibility in Policy Daniel Kahn Gillmor <dkg@fifthhorseman.net> - 2017-08-12 03:40 +0200
Bug#844431: Reproducibility in Policy Russ Allbery <rra@debian.org> - 2017-08-12 05:40 +0200
Bug#844431: Reproducibility in Policy Holger Levsen <holger@layer-acht.org> - 2017-08-12 23:50 +0200
Bug#844431: Reproducibility in Policy Bill Allombert <ballombe@debian.org> - 2017-08-12 12:10 +0200
Bug#844431: Reproducibility in Policy Russ Allbery <rra@debian.org> - 2017-08-12 23:10 +0200
csiph-web