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.

archreproduced builds (forky)graph for forkypercentage tried / queued sources (forky)workers
all
Loading stats...
📈
Loading progress...
ionos20-amd64
ionos21-amd64
ionos22-amd64
ionos23-amd64
ionos24-amd64
ionos25-amd64
amd64
Loading stats...
📈
Loading progress...
osuosl41-amd64
osuosl42-amd64
osuosl43-amd64
osuosl44-amd64
arm64
Loading stats...
📈
Loading progress...
codethink02-arm64
armel (trixie)
Loading stats...
📈
Loading progress...
codethink05-arm64
armhf
Loading stats...
📈
Loading progress...
codethink01-arm64
i386
Loading stats...
📈
Loading progress...
infomaniak0(7|8)-amd64
ppc64el
Loading stats...
📈
Loading progress...
osuosl(6|7)-ppc64el
riscv64
Loading stats...
📈
Loading progress...
riscv64-(01|02|04|06|07|33|34)

Coming soon: 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