1.0.1-2.1 in the archive, ships a compiled extension
built,
ours is 1.0.1-2.1+py315.1.
Nothing recorded is waiting on this one.
published,
1.0.1-2.1+py315.1,
as work request 1224400.
Sent before this one:
1.0.1-2+py315.2.
A version that was sent is spent, whatever came of it.
| Question | Answer | Said by | As of |
|---|---|---|---|
| Why did the build fail? |
unknown
The log was read and says nothing this tool recognises. These are the failures somebody has to look at. |
deps/11 | not dated |
| Which known interpreter change does this failure show? |
module-not-importable
a dependency was not importable. Nothing here says the interpreter caused this. An import that failed usually means the testbed was assembled before the dependency had been rebuilt, which is ours to fix by running it again. ModuleNotFoundError: No module named 'distutils' could not import distutils |
deps/11 | not dated |
| 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 0
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 |
| Is this filed in Debian? |
#1080757
Filed by this round, or adopted from the BTS by its usertag. |
the tracker's own record | not dated |
| has anybody reported this under the usertag? |
1 bug
somebody has already reported this under the round's usertag, so it is tracked; the tag is the only record connecting what was sent to what this tracks #1080757 python-nss: Missing Build-Depends on python3-setuptools |
the BTS usertag | not dated |
| Version | Arch | Kind | Result | Binaries | Interpreters | Closure | Finished |
|---|---|---|---|---|---|---|---|
1.0.1-2.1+py315.1
|
arm64 | test | pass | rebuilt | named none | — | 2026-09-03 20:23 |
1.0.1-2.1+py315.1
|
amd64 | test | pass | rebuilt | named none | — | 2026-09-03 20:22 |
1.0.1-2.1
|
arm64 | test | pass | the archive's (reference arm) | 3.14, 3.15 | — | 2026-09-03 15:29 |
1.0.1-2.1+py315.1
|
arm64 | build | pass | unknown | not read yet | — | 2026-09-03 20:22 |
1.0.1-2.1+py315.1
|
amd64 | build | pass | unknown | not read yet | — | 2026-09-03 20:21 |
1.0.1-2+py315.2
|
amd64 | build | fail | unknown | not read yet | — | 2026-09-01 09:00 |
1.0.1-2+py315.1
|
arm64 | build | fail | unknown | not read yet | — | 2026-08-09 21:43 |
1.0.1-2+py315.1
|
amd64 | build | fail | unknown | not read yet | — | 2026-08-09 21:48 |
1.0.1-2
|
arm64 | test | fail | the archive's (reference arm) | named none | — | 2026-08-02 15:26 |
1.0.1-2
|
amd64 | test | fail | the archive's (reference arm) | named none | — | 2026-08-02 15:26 |
1.0.1-2+py315.1
|
arm64 | build | fail | unknown | not read yet | — | 2026-08-02 20:36 |
1.0.1-2+py315.1
|
amd64 | build | fail | unknown | not read yet | — | 2026-08-02 23:17 |