6.11.2-2 in the archive, ships a compiled extension
build failed,
ours is 6.11.2-2+py315.d.1.
python3-dev-only
build-depend on python3-all-dev instead of python3-dev
Rebuilding it releases 93 packages waiting on it, as this stage last counted.
aborted,
6.11.2-2+py315.d.1,
as work request 1317330,
which ended in work request 1317332.
Which turned out to be build-failed: the workflow ended: build-failed, work request 1317332.
Sent before this one:
6.10.3-3+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 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 |
|---|---|---|---|---|---|---|---|
6.11.2-2+py315.d.1
|
arm64 | build | fail | unknown | not read yet | — | 2026-09-21 15:50 |
6.11.2-2+py315.d.1
|
amd64 | build | fail | unknown | not read yet | — | 2026-09-21 15:46 |
6.11.2-2+py315.d.1
|
all | build | fail | unknown | not read yet | — | 2026-09-21 15:44 |
6.10.3-3
|
arm64 | test | fail | the archive's (reference arm) | named none | — | 2026-09-15 09:23 |
6.10.3-3+py315.d.1
|
arm64 | build | fail | unknown | not read yet | — | 2026-09-15 15:29 |
6.10.3-3+py315.d.1
|
amd64 | build | fail | unknown | not read yet | — | 2026-09-15 15:29 |
6.10.3-3+py315.d.1
|
all | build | fail | unknown | not read yet | — | 2026-09-15 15:28 |