1.3.0-2 in the archive, ships a compiled extension
build failed,
ours is 1.3.0-2+py315.d.1.
Rebuilding it releases 1 package waiting on it, as this stage last counted.
aborted,
1.3.0-2+py315.d.1,
as work request 1272134,
which ended in work request 1272137.
Which turned out to be build-failed: the workflow ended: build-failed, work request 1272137.
| Question | Answer | Said by | As of |
|---|---|---|---|
| does Debian's own test suite pass? |
not tested by debian
Debian runs no autopkgtest for this, so we have no independent baseline: nothing here distinguishes a failure this interpreter caused from one the package always had |
ci.debian.net | not dated |
| does the release team track this? |
dependency level 0
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 unknown, arm64 unknown, armhf unknown, i386 unknown, loong64 unknown, ppc64el unknown, riscv64 unknown, s390x unknown |
release.debian.org, from their ben tracker | 2026-09-16 04:49 UTC |
| Version | Arch | Kind | Result | Binaries | Interpreters | Closure | Finished |
|---|---|---|---|---|---|---|---|
1.3.0-2
|
arm64 | test | pass | the archive's (reference arm) | 3.14, 3.15 | — | 2026-09-14 21:37 |
1.3.0-2
|
amd64 | test | pass | the archive's (reference arm) | 3.14, 3.15 | — | 2026-09-14 21:37 |
1.3.0-2+py315.d.1
|
arm64 | build | fail | unknown | not read yet | — | 2026-09-15 00:49 |
1.3.0-2+py315.d.1
|
amd64 | build | fail | unknown | not read yet | — | 2026-09-15 00:48 |