3.0.4-1 in the archive, ships a compiled extension
built,
ours is 3.0.4-1+py315.d.1.
python3-dev-only
build-depend on python3-all-dev instead of python3-dev
Nothing recorded is waiting on this one.
published,
3.0.4-1+py315.d.1,
as work request 1309774.
Sent before this one:
3.0.0-1+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? |
archive-dependency
Built against the archive's copy of a dependency we have rebuilt. The ordering has not reached it, so this is not the package's own fault. python3-yaml 6.0.3-1+py315.2: we publish 6.0.3-1+py315.d.2 |
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.0.4-1+py315.d.1
|
arm64 | test | pass | rebuilt | named none | — | 2026-09-20 03:09 |
3.0.4-1+py315.d.1
|
amd64 | test | pass | rebuilt | named none | — | 2026-09-20 03:07 |
3.0.4-1+py315.d.1
|
arm64 | build | pass | unknown | not read yet | — | 2026-09-20 03:08 |
3.0.4-1+py315.d.1
|
amd64 | build | pass | unknown | not read yet | — | 2026-09-20 03:06 |
3.0.0-1
|
arm64 | test | fail | the archive's (reference arm) | named none | — | 2026-09-14 21:37 |
3.0.0-1
|
amd64 | test | fail | the archive's (reference arm) | named none | — | 2026-09-14 21:37 |
3.0.0-1+py315.d.1
|
arm64 | build | fail | unknown | not read yet | — | 2026-09-15 01:40 |
3.0.0-1+py315.d.1
|
amd64 | build | fail | unknown | not read yet | — | 2026-09-15 01:40 |