1.29.0-3 in the archive, ships a compiled extension
tests failed,
ours is 1.29.0-3+py315.d.1.
python3-dev-only
build-depend on python3-all-dev instead of python3-dev
Nothing recorded is waiting on this one.
published,
1.29.0-3+py315.d.1,
as work request 1300965.
Sent before this one:
1.29.0-2+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 |
| do Debian's own tests pass? |
archive tests fail
Debian's own tests for this package fail in unstable, so this failure is not the new interpreter's doing. debci answers about the source rather than about the version we rebuilt, which is why the date its run happened is shown. amd64, arm64, last run 2026-08-17 |
ci.debian.net | not dated |
| Version | Arch | Kind | Result | Binaries | Interpreters | Closure | Finished |
|---|---|---|---|---|---|---|---|
1.29.0-3+py315.d.1
|
arm64 | test | fail | rebuilt | named none | — | 2026-09-17 19:47 |
1.29.0-3+py315.d.1
|
amd64 | test | fail | rebuilt | named none | — | 2026-09-17 19:51 |
1.29.0-3
|
arm64 | test | pass | the archive's (reference arm) | 3.14, 3.15 | — | 2026-09-17 15:26 |
1.29.0-3
|
amd64 | test | pass | the archive's (reference arm) | 3.14, 3.15 | — | 2026-09-17 15:26 |
1.29.0-3+py315.d.1
|
arm64 | build | pass | unknown | not read yet | — | 2026-09-17 19:45 |
1.29.0-3+py315.d.1
|
amd64 | build | pass | unknown | not read yet | — | 2026-09-17 19:49 |
1.29.0-2
|
arm64 | test | fail | the archive's (reference arm) | 3.14 | — | 2026-09-16 09:19 |
1.29.0-2
|
amd64 | test | fail | the archive's (reference arm) | 3.14 | — | 2026-09-16 09:19 |
1.29.0-2+py315.d.1
|
arm64 | build | fail | unknown | not read yet | — | 2026-09-16 11:24 |
1.29.0-2+py315.d.1
|
amd64 | build | fail | unknown | not read yet | — | 2026-09-16 11:23 |