10.10-1 in the archive, ships a compiled extension
build failed,
ours is 10.9-1+py315.d.1.
archive has moved on; rebuild before believing this
python3-dev-only
build-depend on python3-all-dev instead of python3-dev
Rebuilding it releases 1 package waiting on it, as this stage last counted.
aborted,
10.9-1+py315.d.1,
as work request 1369138,
which ended in work request 1369140.
Which turned out to be build-failed: the workflow ended: build-failed, work request 1369140.
Sent before this one:
9.5-6+py315.d.1.
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 |
| does the archive build this version? |
archive ftbfs
Debian's own rebuild of the version the archive carries fails too, so this failure is not the new interpreter's doing. It still blocks the transition: nobody can rebuild it until that is fixed. arm64 |
tests.reproducible-builds.org | not dated |
| does Debian's own test suite pass? |
neutral
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 |
|---|---|---|---|---|---|---|---|
10.9-1+py315.d.1
|
arm64 | build | fail | unknown | not read yet | — | 2026-09-28 21:06 |
10.9-1+py315.d.1
|
amd64 | build | fail | unknown | not read yet | — | 2026-09-28 21:15 |
10.9-1+py315.d.1
|
all | build | fail | unknown | not read yet | — | 2026-09-28 22:18 |
9.5-6+py315.d.1
|
arm64 | build | fail | unknown | not read yet | — | 2026-09-17 18:59 |
9.5-6+py315.d.1
|
amd64 | build | fail | unknown | not read yet | — | 2026-09-17 18:59 |
9.5-6+py315.d.1
|
all | build | fail | unknown | not read yet | — | 2026-09-17 18:59 |