6.1.2-2 in the archive, ships a compiled extension
built,
ours is 6.1.2-2+py315.d.2.
Rebuilding it releases 6396 packages waiting on it, as this stage last counted.
published,
6.1.2-2+py315.d.2,
as work request 1277585.
Sent before this one:
6.1.2-2+py315.d.1.
A version that was sent is spent, whatever came of it.
| Question | Answer | Said by | As of |
|---|---|---|---|
| does Debian's own test suite pass? |
neutral
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 |
| does the release team track this? |
dependency level 1
The release team's own tracker lists it, and their dependency level is how the transition is sequenced: a level cannot be read as done while anything below it is outstanding. Their question is what a package's binaries depend on, not what it ships, so their verdict and ours can disagree without either being wrong. amd64 bad, arm64 bad, armhf bad, i386 bad, loong64 bad, ppc64el bad, riscv64 bad, s390x bad |
release.debian.org, from their ben tracker | 2026-09-16 04:49 UTC |
| what did triage decide about the build? |
unknown
Somebody's decision about this failure, not a measurement. The runs beside it are free to disagree with it, which is why both are kept. STALE VERDICT CORRECTED 2026-08-04. Was 'pre-existing' on the strength of a 6.1.2-1 build (cargo: libm ^0.2.6 locked to 0.2.15). That verdict came from testing's 6.1.2-1 because py315-rebuild-source.sh called plain 'apt-get source', and unstable is pinned to priority 150 locally, below testing's 500. sid has had 6.1.2-2 since 2026-08-02, which fixes that FTBFS: drops rust/Cargo.lock at build time and lets cargo resolve against /usr/share/cargo/registry (Closes: #1143288, team upload, built OK locally). Nothing published in the py315 suite for cbor2, so 6.1.2-2 has never been built against 3.15 and its compatibility is unknown. Action: rebuild (now correctly resolves to 6.1.2-2+py315.1) and re-triage on the real result. |
whoever triaged it | 2026-08-16 10:17 UTC |
| Is this filed in Debian? |
#1143288
Filed by this round, or adopted from the BTS by its usertag. |
the tracker's own record | not dated |
| Version | Arch | Kind | Result | Binaries | Interpreters | Closure | Finished |
|---|---|---|---|---|---|---|---|
6.1.2-2+py315.d.2
|
arm64 | test | pass | rebuilt | named none | — | 2026-09-15 10:37 |
6.1.2-2+py315.d.2
|
amd64 | test | pass | rebuilt | named none | — | 2026-09-15 10:40 |
6.1.2-2+py315.d.2
|
arm64 | build | pass | unknown | not read yet | — | 2026-09-15 10:13 |
6.1.2-2+py315.d.2
|
amd64 | build | pass | unknown | not read yet | — | 2026-09-15 10:39 |
6.1.2-2+py315.d.2
|
all | build | pass | unknown | not read yet | — | 2026-09-15 10:36 |
6.1.2-2
|
arm64 | test | fail | the archive's (reference arm) | named none | — | 2026-09-13 15:13 |
6.1.2-2
|
amd64 | test | fail | the archive's (reference arm) | named none | — | 2026-09-13 15:13 |
6.1.2-2+py315.d.1
|
arm64 | build | fail | unknown | not read yet | — | 2026-09-13 17:01 |
6.1.2-2+py315.d.1
|
amd64 | build | fail | unknown | not read yet | — | 2026-09-13 17:10 |
6.1.2-2+py315.d.1
|
all | build | fail | unknown | not read yet | — | 2026-09-13 17:10 |