Differences between revisions 384 and 385
Revision 384 as of 2019-10-01 15:54:58
Size: 8025
Editor: HolgerLevsen
Comment: add new section: solved isses
Revision 385 as of 2019-10-01 16:19:45
Size: 8026
Editor: HolgerLevsen
Comment: shuffle prios once again
Deletions are marked like this. Additions are marked like this.
Line 30: Line 30:
 * [[DebianBug:900837|#900837: Mass-rebuild of packages for reproducible builds]] (blocked by #894441)  * User-facing interfaces (see proof-of-concept in [[DebianBug:863622|#863622: apt: warn when installing packages that are not reproducible]]
Line 34: Line 34:
 * User-facing interfaces (see proof-of-concept in [[DebianBug:863622|#863622: apt: warn when installing packages that are not reproducible]]  * [[DebianBug:900837|#900837: Mass-rebuild of packages for reproducible builds]] (blocked by #894441):

Got a spare moment? Please migrate this to our new webpages


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.


Make a package reproducible

?How to help

Experimental toolchain

Project history

Salsa / Gitlab
Salsa project / Gitlab

Bug reports

Continuous integration


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

These are the critical items necessary to have reproducible builds for at least the required packages of Debian

Annoying but not major

Nice to have

  • Tighten up the Policy definition of "reproducible" to be stricter about environment variables and build paths.
  • Discuss which environment variables we should blacklist or whitelist, 876055.

  • #929397: ftp.d.o: please upload LTS .buildinfo files to ftp-master (this is not relevant yet, as Jessie is the LTS release, while only dpkg from Stretch and newer produces .buildinfo files.)

Also related

  • #895346 [devscripts] devscripts: dcmd --buildinfo is not documented

  • #869567 [devscripts] debsign: doesn't sign multiple .buildinfo in the same changes

  • #898961 [devscripts] dscverify: accept .buildinfo from a build with unsigned .dsc which later was signed

  • #807270 [devscripts] mk-origtargz: create reproducible tarballs and --mtime option

  • #852365 [sbuild] sbuild: append-to-version may overwrite incorrect .buildinfo

  • #923987 [sbuild] Should also send the buildinfo in the build mail

There are many other possible nice-to-haves, e.g., making builds independent of their build directory, making it possible to create archive formats (like tar.gz and zip) with different tools yet result in the same byte order, etc. Many of those are valuable, but they shouldn't distract from getting the results of reproducible builds out to users.

Even more

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

Statistics from the continuous integration platform

Solved issues

CategoryDeveloper CategoryPackaging