6.2.2606+dfsg1-2 in the archive, ships a compiled extension
build failed,
ours is 6.2.2606+dfsg1-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 8 packages waiting on it, as this stage last counted.
aborted,
6.2.2606+dfsg1-1+py315.d.1,
as work request 1281675,
which ended in work request 1281677.
Which turned out to be build-failed: the workflow ended: build-failed, work request 1281677.
| Question | Answer | Said by | As of |
|---|---|---|---|
| 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, last run 2026-10-02 |
ci.debian.net | not dated |
| Version | Arch | Kind | Result | Binaries | Interpreters | Closure | Finished |
|---|---|---|---|---|---|---|---|
6.2.2606+dfsg1-1
|
arm64 | test | fail | the archive's (reference arm) | named none | — | 2026-09-15 21:18 |
6.2.2606+dfsg1-1
|
amd64 | test | fail | the archive's (reference arm) | named none | — | 2026-09-15 21:18 |
6.2.2606+dfsg1-1+py315.d.1
|
arm64 | build | fail | unknown | not read yet | — | 2026-09-15 21:49 |
6.2.2606+dfsg1-1+py315.d.1
|
amd64 | build | fail | unknown | not read yet | — | 2026-09-15 21:51 |
6.2.2606+dfsg1-1+py315.d.1
|
all | build | fail | unknown | not read yet | — | 2026-09-15 21:51 |