buildd.debian.org Open in urlscan Pro
2607:f8f0:614:1::1274:60  Public Scan

Form analysis
1 forms found in the DOM

GET /status/package.php

<form action="/status/package.php" method="get">
  <label for="pkg_field">Package:</label> <input id="pkg_field" type="text" length="30" name="p" value="">
  <label for="suite">Suite:</label> <select name="suite" id="suite">
    <option value="sid" selected="selected">sid</option>
    <option value="trixie">trixie</option>
    <option value="trixie-backports">trixie-backports</option>
    <option value="trixie-backports-sloppy">trixie-backports-sloppy</option>
    <option value="bookworm">bookworm</option>
    <option value="bookworm-backports">bookworm-backports</option>
    <option value="bookworm-backports-sloppy">bookworm-backports-sloppy</option>
    <option value="bullseye">bullseye</option>
    <option value="bullseye-security">bullseye-security</option>
    <option value="bullseye-backports">bullseye-backports</option>
    <option value="bullseye-backports-sloppy">bullseye-backports-sloppy</option>
    <option value="experimental">experimental</option>
  </select>
  <input type="submit" value="Go">
  <br>
  <span class="buttons tiny">
    <input type="checkbox" name="compact" value="compact">Compact mode <input type="checkbox" name="comaint" value="yes">Co-maintainers </span>
</form>

Text Content

DEBIAN PACKAGE AUTO-BUILDING


DELIVERING YOUR FAVOURITE PACKAGE ON YOUR ARCHITECTURE ASAP


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 (120) X X X X X X
(2002/6) X (1) X X X (0/1) X X (1) X X X (0/1) X (4/1) X (4) 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/7) X (0/4) X (0/7) X (0/7) 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 X X
(0/5) X (0/5) X (0/5) X (0/5) X (0/5) X (0/5) X (0/5) X (0/5) X (0/5)
bullseye-security X X X X X X X X X X bullseye-backports X X X X X X X X X X
bullseye-backports-sloppy X X X X X X X X X X experimental X X (24) X X X X X X
(172) X X X (1) X X X X (0/1) X X X X 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



Package: Suite: sid trixie trixie-backports trixie-backports-sloppy bookworm
bookworm-backports bookworm-backports-sloppy bullseye bullseye-security
bullseye-backports bullseye-backports-sloppy experimental
Compact mode Co-maintainers




NEWEST BUILD LOGS

 * Aug 30, 01:45:22 spirv-tools 2024.3-1 on m68k in sid: successful (all arches)
 * Aug 30, 01:42:42 ben 1.7+b2 on alpha in sid: successful (all arches)
 * Aug 30, 01:40:36 ppx-assert 0.17.0-1+b4 on alpha in sid: successful (all
   arches)
 * Aug 30, 01:37:42 slepc 3.21.1+dfsg1-1exp2 on m68k in experimental: successful
   (all arches)
 * Aug 30, 01:37:34 lasso 2.8.2-4 on alpha in sid: successful (all arches)
 * Aug 30, 01:36:19 racket 8.14+dfsg1-1 on armhf in sid: successful (all arches)
 * Aug 30, 01:34:35 gcc-snapshot 1:20240829-1 on powerpc in sid: successful (all
   arches)
 * Aug 30, 01:32:20 kwin 4:6.1.4-1 on loong64 in experimental: successful (all
   arches)
 * Aug 30, 01:29:36 r-base 4.4.1-2 on sparc64 in sid: successful (all arches)
 * Aug 30, 01:24:56 gcc-snapshot 1:20240829-1 on loong64 in sid: successful (all
   arches)
 * Aug 30, 01:23:52 openssh 1:9.8p1-8 on hppa in sid: successful (all arches)
 * Aug 30, 01:22:55 openssh 1:9.8p1-8 on m68k in sid: successful (all arches)
 * Aug 30, 01:22:43 ktextwidgets 5.115.0-2 on alpha in sid: successful (all
   arches)
 * Aug 30, 01:17:29 wacomtablet 6.1.4-1 on loong64 in experimental: successful
   (all arches)
 * Aug 30, 01:16:57 ppx-hash 0.17.0-1+b3 on alpha in sid: successful (all
   arches)
 * Aug 30, 01:16:53 mesa 24.2.1-1 on riscv64 in experimental: successful (all
   arches)
 * Aug 30, 01:16:19 gcc-snapshot 1:20240829-1 on amd64 in sid: successful (all
   arches)
 * Aug 30, 01:15:38 print-manager 6:6.1.4-1 on loong64 in experimental:
   successful (all arches)
 * Aug 30, 01:14:47 asymptote 2.90+ds-1 on alpha in sid: successful (all arches)
 * Aug 30, 01:13:24 plasma-vault 6.1.4-1 on loong64 in experimental: successful
   (all arches)
 * Aug 30, 01:11:31 plasma-welcome 6.1.4-1 on loong64 in experimental:
   successful (all arches)
 * Aug 30, 01:09:43 ppx-import 1.11.0-2+b3 on alpha in sid: successful (all
   arches)
 * Aug 30, 01:08:09 ocaml-uri 4.4.0-1+b3 on alpha in sid: successful (all
   arches)
 * Aug 30, 01:06:42 plasma-sdk 6.1.4-1 on loong64 in experimental: successful
   (all arches)
 * Aug 30, 01:05:19 plasma-nm 4:6.1.4-2 on loong64 in experimental: successful
   (all arches)

more


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.