Differences between revisions 362 and 363
Revision 362 as of 2018-06-15 08:28:15
Size: 5030
Editor: lamby
Comment:
Revision 363 as of 2018-08-13 07:21:06
Size: 5127
Editor: lamby
Comment:
Deletions are marked like this. Additions are marked like this.
Line 22: Line 22:
 * [[DebianBug:869184|#869184: dpkg: source uploads including _amd64.buildinfo cause problems]]

It should be possible to reproduce, byte for byte, every build of every package in Debian. More information about reproducible builds in general are available at reproducible-builds.org.

About
About

Howto
Make a package reproducible

Contribute
How to help

Toolchain
Experimental toolchain

History
Project history

Salsa
Salsa project

Bugs
Bug reports

Jenkins
Continuous integration

Status

Reproducible builds of Debian as a whole is still not a reality, though individual reproducible builds of packages are possible and being done. So while we are making very good progress, it is a stretch to say that Debian is reproducible.

  • Most packages built in sid today are reproducible under a fixed build-path and environment.

  • We have a new control file *.buildinfo that records the build environment, see deb-buildinfo for reference. Older design drafts are here.

  • We have a continuous integration platform that builds and immediately rebuilds packages. With this we can detect problems related to timestamps, file ordering, CPU usage, (pseudo-)randomness and other things.

  • We are examining packages and sorting out common problems.

  • Many patches have already been submitted, and we are continuously writing new ones.

  • You can check which packages installed on your system are still unreproducible by using the reproducible-check script in the devscripts package.

Big outstanding issues

Next

For more concrete tasks to be done, look at how to contribute.

Statistics from the continuous integration platform


CategoryDebianDevelopment