6.1.1-1 in the archive, ships a compiled extension
tests failed,
ours is 6.1.1-1+py315.1,
waiting on ceph.
python3-dev-only
build-depend on python3-all-dev instead of python3-dev
tests ran 3.14
Nothing recorded is waiting on this one.
published,
6.1.1-1+py315.1,
as work request 1102514.
| Question | Answer | Said by | As of |
|---|---|---|---|
| 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 |
| 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 2025-01-24 |
ci.debian.net | not dated |
| did its tests run this interpreter? |
others only
Its tests named the interpreters they ran and ours was not among them, so whatever they say is about those. A census blocker explains most of them: the package builds against whatever `python3-dev` points at. Without one, a retest under this interpreter would settle it. ran 3.14 |
the harness that ran them | not dated |
| Version | Arch | Kind | Result | Binaries | Interpreters | Closure | Finished |
|---|---|---|---|---|---|---|---|
6.1.1-1+py315.1
|
arm64 | test | fail | rebuilt | 3.14 | — | 2026-08-24 14:16 |
6.1.1-1+py315.1
|
amd64 | test | fail | rebuilt | 3.14 | — | 2026-08-24 14:17 |
6.1.1-1+py315.1
|
arm64 | build | pass | unknown | not read yet | — | 2026-08-24 14:07 |
6.1.1-1+py315.1
|
amd64 | build | pass | unknown | not read yet | — | 2026-08-24 14:15 |
6.1.1-1+py315.1
|
all | build | pass | unknown | not read yet | — | 2026-08-24 14:15 |