3.64.2-1 in the archive
built,
ours is 3.64.2-1+py315.1.
Rebuilding it releases 1 package waiting on it, as this stage last counted.
published,
3.64.2-1+py315.1,
as work request 1324900.
Sent before this one:
3.38.0-1+py315.1.
A version that was sent is spent, whatever came of it.
| Question | Answer | Said by | As of |
|---|---|---|---|
| Why did the build fail? |
superseded-dependency
Built against our own rebuild of a dependency, one generation back. The run is evidence, unlike an archive copy: re-run it against the current suite before reading the failure. python3-coverage 7.8.2+dfsg1-1+py315.1: we publish 7.16.1+dfsg1-1+py315.1 python3-pandas-lib 2.3.3+dfsg-3.1+py315.7: we publish 2.3.3+dfsg-6+py315.2 |
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 ModuleNotFoundError: No module named 'yaml' could not import yaml |
deps/11 | not dated |
| 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 |
| Version | Arch | Kind | Result | Binaries | Interpreters | Closure | Finished |
|---|---|---|---|---|---|---|---|
3.64.2-1+py315.1
|
amd64 | test | pass | rebuilt | named none | — | 2026-09-22 21:46 |
3.64.2-1
|
amd64 | test | pass | archive | 3.14, 3.15 | — | 2026-09-22 21:09 |
3.64.2-1+py315.1
|
all | build | pass | unknown | not read yet | — | 2026-09-22 21:43 |
3.38.0-1+py315.1
|
all | build | fail | unknown | not read yet | — | 2026-09-07 14:06 |