Differences between revisions 338 and 339
Revision 338 as of 2016-11-10 18:18:54
Size: 5149
Editor: HolgerLevsen
Comment: status needs more updates than this, but enotime atm…
Revision 339 as of 2016-11-15 13:12:09
Size: 5119
Editor: HolgerLevsen
Comment: update status
Deletions are marked like this. Additions are marked like this.
Line 10: Line 10:
Reproducible builds in Debian are still at the experimental stage. While we are making very good progress, it is a ''stretch'' to say that Debian is reproducible or even partially reproducible until the needed changes are integrated in the main distribution. Reproducible builds of Debian as a whole are still not a reality, though individual reproducible builds of packages are possible. So while we are making very good progress, it is a ''stretch'' to say that Debian is reproducible.

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

Alioth
Alioth project

Bugs
Bug reports

Jenkins
Continuous integration

Status

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

Statistics from the continuous integration platform

Next

  • Identify more common problems.
  • Get toolchain changes integrated.
  • Start a campaign to get developers to fix their packages.
  • Get .buildinfo files in the archive.

  • Get dpkg supporting reproducible builds upload to unstable.

  • Require matching binary packages from the developer and a buildd before accepting the package in the archive. This could initially be opt-in.

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

Drivers

  • h01ger
  • lamby
  • infinity0