Debian Package Auto-Building (original) (raw)

About this site

Debian employs a network of autobuilding machines delivering package builds for a diverse set of CPU architectures. buildd.debian.org coordinates those builds using a central host called wanna-build. Build log and states within this database can be found on this site. More information about the autobuilder network is available on the main Debian website.

Build states

| | all | alpha | amd64 | arm64 | armel | armhf | hppa | hurd64 | hurd | i386 | lg64 | m68k | mips64el | mipsel | ppc | ppc64 | ppc64el | rv64 | s390x | sh4 | sparc64 | x32 | | | ------------------------- | ------------------------------------------------------------------- | -------------------------------------------------------------- | --------------------------------------------------------------------- | --------------------------------------------------------------------- | -------------------------------------------------------------- | --------------------------------------------------------------------- | ------------------------------------------------------- | ------------------------------------------------------------------- | ------------------------------------------------------------ | -------------------------------------------------------------------- | ---------------------------------------------------------- | ------------------------------------------------------------ | ----------------------------------------------------------------- | --------------------------------------------------------------- | ---------------------------------------------------------------- | -------------------------------------------------------- | ---------------------------------------------------------------- | --------------------------------------------------------------- | -------------------------------------------------------------- | ----------------------------------------------------------- | ---------------------------------------------------------- | ------------------------------------------------------ | | sid | X | X (2036) | X | X | X | X | X (2) | X (1719/5) | X (1/1) | X | X (0/3) | X (51/1) | X (1) | | X | X | X | X (105) | X (2) | X (233) | X (0/1) | X (0/1) | | trixie | X | | X | X | X | X | | | | X | | | X | | | | X | X | X | | | | | trixie-backports | | | | | | | | | | | | | | | | | | | | | | | | trixie-backports-sloppy | | | | | | | | | | | | | | | | | | | | | | | | bookworm | X | | X (0/6) | X (0/4) | X (0/6) | X (0/4) | | | | X (0/6) | | | X (0/6) | X (0/4) | | | X (0/5) | | X (0/5) | | | | | bookworm-backports | X | | X | X | X | X | | | | X | | | X | X | | | X | | X | | | | | bookworm-backports-sloppy | | | | | | | | | | | | | | | | | | | | | | | | bullseye-security | X | | X | X | | X | | | | X | | | | | | | | | | | | | | bullseye-backports | X | | X | X | | X | | | | X | | | | | | | | | | | | | | bullseye-backports-sloppy | X | | X | X | | X | | | | X | | | | | | | | | | | | | | experimental | X (1) | X (106) | X | X (1) | X | X | X | X (172) | X | X (1) | X | X (21) | X | | X (0/1) | X | X (1) | X (25) | X (1) | X (63) | X | X |

The numbers show how many packages are in needs-build state. Please note that even a high number doesn't necessarily mean that there is a problem with the architecture, as there are a couple of good reasons why packages in that state don't get built: This might be because they are non-free but the architectures buildds only build main and contrib packages. Or there is some depended-on package which doesn't want to get installed on the architecture (good chance in sid with virtual packages for that). The second number shows how many packages are in state built or uploaded since more than a day (but that might also be due to new-queues).

Query a package's state

Newest build logs

Nov 18, 07:45:30 python-fuse 2:1.0.9-1 on armel in sid: successful (all arches)
Nov 18, 07:45:10 composer 2.8.3-1 on all in sid: successful (all arches)
Nov 18, 07:44:51 python-fuse 2:1.0.9-1 on arm64 in sid: successful (all arches)
Nov 18, 07:43:00 python-fuse 2:1.0.9-1 on amd64 in sid: successful (all arches)
Nov 18, 07:42:34 python-fuse 2:1.0.9-1 on i386 in sid: successful (all arches)
Nov 18, 07:42:32 python-fuse 2:1.0.9-1 on armhf in sid: successful (all arches)
Nov 18, 07:42:29 linux 6.11.9-1 on x32 in sid: successful (all arches)
Nov 18, 07:42:09 python-fuse 2:1.0.9-1 on ppc64el in sid: successful (all arches)
Nov 18, 07:35:52 pianobooster 1.0.0-4 on sh4 in sid: successful (all arches)
Nov 18, 07:35:28 pygame 2.6.0-2+b1 on m68k in sid: successful (all arches)
Nov 18, 07:34:11 python-cartopy 0.24.1+dfsg-1+b1 on sh4 in sid: successful (all arches)
Nov 18, 07:31:47 slixmpp 1.8.5-1+b3 on m68k in sid: given-back (all arches)
Nov 18, 07:30:58 arc-gui-clients 0.4.6-7+b3 on m68k in sid: successful (all arches)
Nov 18, 07:29:45 binutils 2.43.50.20241112-1 on i386 in experimental: given-back (all arches)
Nov 18, 07:28:52 py3exiv2 0.12.0-2+b1 on hppa in sid: successful (all arches)
Nov 18, 07:28:40 qemu 1:9.2.0~rc0+ds-1 on all in experimental: given-back (all arches)
Nov 18, 07:28:23 linux 6.11.9-1 on all in sid: successful (all arches)
Nov 18, 07:27:53 binutils 2.43.50.20241112-1 on ppc64el in experimental: given-back (all arches)
Nov 18, 07:25:53 libftdi1 1.5-7+b1 on hppa in sid: successful (all arches)
Nov 18, 07:24:24 astroscrappy 1.2.0-1+b2 on riscv64 in sid: successful (all arches)
Nov 18, 07:23:28 scipy 1.13.1-6 on m68k in sid: successful (all arches)
Nov 18, 07:19:53 opentsne 1.0.2-2+b1 on riscv64 in sid: successful (all arches)
Nov 18, 07:19:52 binutils 2.43.50.20241112-1 on i386 in experimental: given-back (all arches)
Nov 18, 07:19:47 systemd 257~rc2-3 on alpha in sid:failed(all arches)
Nov 18, 07:17:36 criu 3.19-3 on arm64 in sid:failed(all arches)

Statistics

You can find some statistics on this page.

How to request binNMUs or give-backs

Binary NMUs (binNMUs) are generally scheduled by the release team. Please see their Asking for wanna-build actions primer for details. Retry requests (give-backs) should be sent to $arch@buildd.debian.org.

Source code

The source code repositories for the Debian Buildds is available at https://salsa.debian.org/wb-team/. wanna-build is available as a Git repository. Packages-arch-specific has its own Git repository with one branch per release. sbuild and buildd live together in the sbuild salsa repository.

Furthermore every DD is free to inspect the running setup on buildd.debian.org.