reproduce.debian.net

Attempts to bit-for-bit identically rebuild each Debian binary package found in the distribution archive, using the .buildinfo file produced when the buildd originally built the package.

For each distributed package, rebuilderd calls debrebuild that calls debootsnap, mmdebstrap and finally sbuild to build that package within a user namespace.

buildinfos.debian.net provides .buildinfo files for each distributed binary package. (see #763822, #929397)
debootsnap uses snapshot.debian.org to retrieve the exact same version of each build dependency package (which was used for the "original build"). (see #1096129)
The goal is to replicate the same build process that is used by Debian during package publication -- not to seek out additional sources of variance.
Variance testing, used to find factors that can prevent packages from rebuilding reproducibly, will continue at https://tests.reproducible-builds.org/debian/reproducible.html.
If you are wondering why we are doing this at all, then hopefully the Reproducible Builds website will explain why this is useful.

`suite/arch`	reproduced builds	graph	percentage tried / queued sources	workers
trixie/all	Loading stats...	📈	Loading progress...	ionos17-amd64
trixie/amd64	Loading stats...	📈	Loading progress...	osuosl4-amd64
trixie/arm64	Loading stats...	📈	Loading progress...	codethink02-arm64
trixie/armel	Loading stats...	📈	Loading progress...	codethink05-arm64
trixie/armhf	Loading stats...	📈	Loading progress...	codethink01-arm64
trixie/i386	Loading stats...	📈	Loading progress...	infomaniak0(7\|8)-amd64
trixie/ppc64el	Loading stats...	📈	Loading progress...	osuosl(6\|7)-ppc64el
trixie/riscv64	Loading stats...	📈	Loading progress...	riscv64-(01\|02\|04\|06\|07\|33\|34)

Coming soon: forky, unstable... & s390x! Help welcome:

We want more and independent rebuilders

Do you have hardware idling? Because, for sure, Debian rebuilding Debian is superb and it's something we've been working on for years! Yet we still want more: we also want independent rebuilders, and we want them in a diverse variety of setups and settings...! And then we'll want anyone to be able to act on this data too.

How to evaluate a trixie system


	    sudo apt install debian-repro-status ; debian-repro-status

(Because we only test trixie right now, results on unstable and forky will vary.)

Documentation hints for rebuilderd

#1109459: rebuilderd: config files and scripts for a simple one machine setup
#1110036: rebuilderd: create rebuilderd user
#1110037: rebuilderd-worker: config files and scripts for a simple one machine setup
#1110038: rebuilderd-worker: create rebuilderd-worker user with subuid
How to setup rebuilderd on Debian. (outdated)
How to use/control rebuilderd. (outdated)
https://r.d.n/$arch/api/v0/pkgs/list (JSON)
https://r.d.n/$arch/stats/db-backup/ (rebuilderd database backups)

pew pew, rebuilderd using debrebuild to reproduce what Debian distributes via ftp.debian.org. ♥️
This setup is in its infancy, even though by now everything is in trixie. Still, please don't consider any URLs as stable here, and more to the point, especially don't take any numbers here seriously, unless...!?!
Oh, and in case you are wondering why we are doing this, then hopefully the Reproducible Builds website will explain why this is useful.
Static content last modified: 2025-08-28
contact: IRC preferred: #debian-reproducible on OFTC or mail to holger@d.o