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.

suite/archreproduced buildsgraphpercentage tried / queued sourcesworkers
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-0(1|2|6|7)

Coming soon: s390x and unstable/*!
(We currently have no idea how to get access to mips64el systems...)

We want 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 don't test unstable yet, results on unstable may vary, though due to the freeze not that much.)

Documentation hints for rebuilderd

# 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)