1.0~b2-4 in the archive, ships a compiled extension
build failed,
ours is 1.0~b2-4+py315.d.1.
Nothing recorded is waiting on this one.
aborted,
1.0~b2-4+py315.d.1,
as work request 1291751,
which ended in work request 1291753.
Which turned out to be build-failed: the workflow ended: build-failed, work request 1291753.
| Question | Answer | Said by | As of |
|---|---|---|---|
| does the release team track this? |
dependency level 8
The release team's own tracker lists it, and their dependency level is how the transition is sequenced: a level cannot be read as done while anything below it is outstanding. Their question is what a package's binaries depend on, not what it ships, so their verdict and ours can disagree without either being wrong. amd64 bad, arm64 bad, armhf unknown, i386 unknown, loong64 unknown, ppc64el unknown, riscv64 unknown, s390x unknown not in testing, so sid only |
release.debian.org, from their ben tracker | 2026-09-17 04:49 UTC |
| Version | Arch | Kind | Result | Binaries | Interpreters | Closure | Finished |
|---|---|---|---|---|---|---|---|
1.0~b2-4
|
arm64 | test | fail | the archive's (reference arm) | named none | — | 2026-09-16 21:21 |
1.0~b2-4
|
amd64 | test | fail | the archive's (reference arm) | named none | — | 2026-09-16 21:21 |
1.0~b2-4+py315.d.1
|
arm64 | build | fail | unknown | not read yet | — | 2026-09-16 23:09 |
1.0~b2-4+py315.d.1
|
amd64 | build | fail | unknown | not read yet | — | 2026-09-16 23:09 |
1.0~b2-4+py315.d.1
|
all | build | fail | unknown | not read yet | — | 2026-09-16 23:09 |