2.8.4-1 in the archive, ships a compiled extension
built,
ours is 2.8.4-1+py315.3,
waiting on python-charset-normalizer, scipy, skimage.
Rebuilding it releases 2 packages waiting on it, as this stage last counted.
published,
2.8.4-1+py315.3,
as work request 1267120.
Sent before this one:
2.8.4-1+py315.1, 2.8.4-1+py315.2.
A version that was sent is spent, whatever came of it.
| Question | Answer | Said by | As of |
|---|---|---|---|
| Why did the build fail? |
dependencies-unsatisfied
apt could not assemble the build chroot, so the build never started. Nothing about the package was tried, and retrying it changes nothing. |
deps/11 | not dated |
| does the release team track this? |
dependency level 5
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 unknown, ppc64el unknown, riscv64 unknown, s390x unknown not in testing, so sid only |
release.debian.org, from their ben tracker | 2026-09-16 04:49 UTC |
| Version | Arch | Kind | Result | Binaries | Interpreters | Closure | Finished |
|---|---|---|---|---|---|---|---|
2.8.4-1+py315.3
|
arm64 | test | pass | rebuilt | named none | — | 2026-09-14 19:04 |
2.8.4-1
|
arm64 | test | fail | the archive's (reference arm) | named none | — | 2026-09-14 15:27 |
2.8.4-1+py315.3
|
arm64 | build | pass | unknown | not read yet | — | 2026-09-14 18:54 |
2.8.4-1+py315.2
|
arm64 | build | fail | unknown | not read yet | — | 2026-09-02 13:30 |
2.8.4-1+py315.1
|
amd64 | build | fail | unknown | not read yet | — | 2026-08-20 08:43 |