3.4.1-3 in the archive, ships a compiled extension
built,
ours is 3.4.1-3+py315.6.
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,
3.4.1-3+py315.6,
as work request 1015922.
Sent before this one:
3.4.1-3+py315.1, 3.4.1-3+py315.2, 3.4.1-3+py315.3, 3.4.1-3+py315.4, 3.4.1-3+py315.5.
A version that was sent is spent, whatever came of it.
| Question | Answer | Said by | As of |
|---|---|---|---|
| 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 |
| 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 |
|---|---|---|---|---|---|---|---|
3.4.1-3+py315.6
|
arm64 | test | pass | rebuilt | 3.14 | — | 2026-08-17 08:38 |
3.4.1-3+py315.6
|
amd64 | test | pass | rebuilt | 3.14 | — | 2026-08-17 08:31 |
3.4.1-3+py315.6
|
arm64 | build | pass | unknown | not read yet | — | 2026-08-17 08:32 |
3.4.1-3+py315.6
|
amd64 | build | pass | unknown | not read yet | — | 2026-08-17 08:30 |
3.4.1-3
|
arm64 | test | pass | the archive's (reference arm) | 3.14 | — | 2026-08-15 21:27 |
3.4.1-3
|
amd64 | test | pass | the archive's (reference arm) | 3.14 | — | 2026-08-15 21:27 |
3.4.1-1
|
arm64 | test | pass | the archive's (reference arm) | 3.14 | — | 2026-08-02 15:26 |
3.4.1-1
|
amd64 | test | pass | the archive's (reference arm) | 3.14 | — | 2026-08-02 15:26 |