1.17.1-5 in the archive, ships a compiled extension
built,
ours is 1.17.1-5+py315.1,
waiting on matplotlib.
Rebuilding it releases 17 packages waiting on it, as this stage last counted.
published,
1.17.1-5+py315.1,
as work request 1016583.
| Question | Answer | Said by | As of |
|---|---|---|---|
| Why did the build fail? |
archive-dependency
Built against the archive's copy of a dependency we have rebuilt. The ordering has not reached it, so this is not the package's own fault. python3-brotli 1.2.0-3.1+py315.2: we publish 1.2.0-4+py315.1 python3-cffi-backend 2.0.0-3+py315.1: we publish 2.1.1-1+py315.1 python3-charset-normalizer 3.4.7-2: we publish 3.4.7-2+py315.1 python3-contourpy 1.3.3-2: we publish 1.3.3-2+py315.1 python3-debugpy 1.8.20+ds-1: we publish 1.8.20+ds-2+py315.2 python3-fonttools 4.62.1-7: we publish 4.62.1-7+py315.1 python3-greenlet 3.3.2-4: we publish 3.3.2-4+py315.1 python3-lz4 4.4.5+dfsg-1: we publish 4.4.5+dfsg-1+py315.1 python3-matplotlib 3.10.9+dfsg1-1: we publish 3.10.9+dfsg1-1+py315.1 python3-tornado 6.5.5-4: we publish 6.5.5-4+py315.1 python3-yaml 6.0.3-1+py315.1: we publish 6.0.3-1+py315.2 python3-zmq 27.1.0-1+b1: we publish 27.1.0-1+py315.1 python3-zopfli 0.4.3-1+py315.1: we publish 0.4.3-2+py315.1 |
deps/11 | not dated |
| Which known interpreter change does this failure show? |
module-not-importable
a dependency was not importable. Nothing here says the interpreter caused this. An import that failed usually means the testbed was assembled before the dependency had been rebuilt, which is ours to fix by running it again. E ImportError: cannot import name '_c_internal_utils' from partially initialized module 'matplotlib' (most likely due to a circular import) (/usr/lib/python3/dist-packages/matplotlib/__init__.py) |
deps/11 | not dated |
| does the release team track this? |
dependency level 4
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.17.1-5+py315.1
|
arm64 | test | pass | rebuilt | named none | superseded-rebuild | 2026-08-17 14:55 |
1.17.1-5+py315.1
|
amd64 | test | pass | rebuilt | named none | superseded-rebuild | 2026-08-17 14:21 |
1.17.1-5+py315.1
|
arm64 | build | pass | unknown | not read yet | — | 2026-08-17 13:57 |
1.17.1-5+py315.1
|
amd64 | build | pass | unknown | not read yet | — | 2026-08-17 13:20 |
1.17.1-5+py315.1
|
all | build | pass | unknown | not read yet | — | 2026-08-17 13:50 |
1.17.1-5+py315.1
|
all | build | fail | unknown | not read yet | — | 2026-08-16 08:08 |