1.35.0-4 in the archive, ships a compiled extension
built,
ours is 1.35.0-4+py315.1,
waiting on matplotlib, pykdtree, python-cartopy, python-pyproj, python-shapely, rasterio, scipy.
Rebuilding it releases 1 package waiting on it, as this stage last counted.
published,
1.35.0-4+py315.1,
as work request 1245620.
Sent before this one:
1.35.0-3+py315.1, 1.35.0-3+py315.2.
A version that was sent is spent, whatever came of it.
| 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 |
| 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. /usr/lib/python3/dist-packages/xarray/core/dataarray.py:416: WARNING: Failed guarded type import in 'xarray.core.dataarray': ModuleNotFoundError("No module named 'iris'") [sphinx_autodoc_typehints.guarded_import] could not import iris |
deps/11 | not dated |
| does the release team track this? |
dependency level 10
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.35.0-4+py315.1
|
arm64 | test | pass | rebuilt | named none | — | 2026-09-09 09:59 |
1.35.0-4+py315.1
|
amd64 | test | pass | rebuilt | named none | — | 2026-09-09 10:04 |
1.35.0-4+py315.1
|
arm64 | build | pass | unknown | not read yet | — | 2026-09-09 09:16 |
1.35.0-4+py315.1
|
amd64 | build | pass | unknown | not read yet | — | 2026-09-09 09:56 |
1.35.0-4+py315.1
|
all | build | pass | unknown | not read yet | — | 2026-09-09 09:48 |
1.35.0-3.1+py315.2
|
arm64 | build | pass | unknown | not read yet | — | 2026-09-06 15:31 |
1.35.0-3.1+py315.2
|
amd64 | build | pass | unknown | not read yet | — | 2026-09-06 15:27 |
1.35.0-3.1+py315.2
|
all | build | pass | unknown | not read yet | — | 2026-09-06 15:26 |
1.35.0-3.1+py315.2
|
arm64 | build | fail | unknown | not read yet | — | 2026-09-06 15:01 |
1.35.0-3.1+py315.2
|
amd64 | build | fail | unknown | not read yet | — | 2026-09-06 15:05 |
1.35.0-3.1+py315.2
|
all | build | fail | unknown | not read yet | — | 2026-09-06 15:04 |
1.35.0-3
|
arm64 | test | fail | the archive's (reference arm) | 3.14, 3.15 | — | 2026-09-02 08:46 |
1.35.0-3
|
amd64 | test | fail | the archive's (reference arm) | 3.14, 3.15 | — | 2026-09-02 08:43 |
1.35.0-3+py315.2
|
arm64 | build | fail | unknown | not read yet | — | 2026-09-02 08:51 |
1.35.0-3+py315.2
|
amd64 | build | fail | unknown | not read yet | — | 2026-09-02 08:46 |
1.35.0-3+py315.2
|
all | build | fail | unknown | not read yet | — | 2026-09-02 08:46 |
1.35.0-3+py315.1
|
amd64 | build | fail | unknown | not read yet | — | 2026-08-19 06:19 |