1.9.25-1 in the archive, ships a compiled extension
built,
ours is 1.9.25-1+py315.2,
waiting on subversion.
Nothing recorded is waiting on this one.
published,
1.9.25-1+py315.2,
as work request 1242020.
| Question | Answer | Said by | As of |
|---|---|---|---|
| Why did the build fail? |
unknown
The log was read and says nothing this tool recognises. These are the failures somebody has to look at. |
deps/11 | not dated |
| does Debian's own test suite pass? |
neutral
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 1
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 bad, i386 bad, loong64 bad, ppc64el bad, riscv64 bad, s390x bad |
release.debian.org, from their ben tracker | 2026-09-16 04:49 UTC |
| Version | Arch | Kind | Result | Binaries | Interpreters | Closure | Finished |
|---|---|---|---|---|---|---|---|
1.9.25-1+py315.2
|
arm64 | test | pass | rebuilt | named none | — | 2026-09-08 07:52 |
1.9.25-1+py315.2
|
amd64 | test | pass | rebuilt | named none | — | 2026-09-08 07:49 |
1.9.25-1+py315.2
|
arm64 | build | pass | unknown | not read yet | — | 2026-09-08 07:51 |
1.9.25-1+py315.2
|
amd64 | build | pass | unknown | not read yet | — | 2026-09-08 07:48 |
1.9.25-1
|
arm64 | test | pass | the archive's (reference arm) | named none | — | 2026-08-10 03:35 |
1.9.25-1
|
amd64 | test | pass | the archive's (reference arm) | named none | — | 2026-08-10 03:35 |
1.9.25-1+py315.1
|
arm64 | build | fail | unknown | not read yet | — | 2026-08-10 08:08 |