1.4.8-1 in the archive, ships a compiled extension
build failed,
ours is 1.4.8-1+py315.d.1.
python3-dev-only
build-depend on python3-all-dev instead of python3-dev
Nothing recorded is waiting on this one.
aborted,
1.4.8-1+py315.d.1,
as work request 1290841,
which ended in work request 1290867.
Which turned out to be build-failed: the workflow ended: build-failed, work request 1290867.
| 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. amd64 |
tests.reproducible-builds.org | 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 |
|---|---|---|---|---|---|---|---|
1.4.8-1
|
arm64 | test | fail | the archive's (reference arm) | named none | — | 2026-09-16 21:21 |
1.4.8-1
|
amd64 | test | fail | the archive's (reference arm) | named none | — | 2026-09-16 21:21 |
1.4.8-1+py315.d.1
|
arm64 | build | fail | unknown | not read yet | — | 2026-09-16 22:23 |
1.4.8-1+py315.d.1
|
amd64 | build | fail | unknown | not read yet | — | 2026-09-16 22:40 |
1.4.8-1+py315.d.1
|
all | build | fail | unknown | not read yet | — | 2026-09-16 22:34 |