3.5.1-1 in the archive, ships a compiled extension
pending,
ours is 3.5.1-1+py315.2.
Nothing recorded is waiting on this one.
published,
3.5.1-1+py315.1.
| 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 |
| 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? |
fixed
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. Resolver-only failure, build never ran: librust-ed25519-dalek-2+default-dev had no provider in sid when WR 980119/980121 ran (2026-08-02), so librust-sequoia-openpgp-dev 2.3.0-1 was uninstallable. The crate landed since (librust-ed25519-dalek-dev 2.2.0+dfsg-1+b1 provides it). Rebuilt 2026-08-04 as 3.5.1-1+py315.1: sbuild amd64+arm64 Success (WR 986439/986440), autopkgtest amd64+arm64 Success (986445/986446), published (986449). Not a 3.15 issue. NB sweep-state recorded 'timeout' while debusine had 3 completed failures - the driver lost the result. |
whoever triaged it | 2026-08-16 10:17 UTC |
No run in this phase yet — it is pending.