3.64.2-1 in the archive
build failed,
ours is 3.38.0-1+py315.d.1.
archive has moved on; rebuild before believing this
Rebuilding it releases 2 packages waiting on it, as this stage last counted.
aborted,
3.38.0-1+py315.d.1,
as work request 1301399,
which ended in work request 1301401.
Which turned out to be build-failed: the workflow ended: build-failed, work request 1301401.
| 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. 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.38.0-1+py315.d.1
|
all | build | fail | unknown | not read yet | — | 2026-09-17 21:47 |