2.0.2-9 in the archive, ships a compiled extension
built,
ours is 2.0.2-9+py315.d.1.
Nothing recorded is waiting on this one.
published,
2.0.2-9+py315.d.1,
as work request 1285880.
| Question | Answer | Said by | As of |
|---|---|---|---|
| does the release team track this? |
dependency level 5
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? |
#1143318
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 #1143318 gyoto: FTBFS: dpkg-buildpackage: error: debian/rules binary subprocess failed with exit status 2 |
the BTS usertag | not dated |
| Version | Arch | Kind | Result | Binaries | Interpreters | Closure | Finished |
|---|---|---|---|---|---|---|---|
2.0.2-9+py315.d.1
|
arm64 | test | pass | rebuilt | named none | — | 2026-09-16 10:45 |
2.0.2-9+py315.d.1
|
amd64 | test | pass | rebuilt | named none | — | 2026-09-16 10:23 |
2.0.2-9
|
arm64 | test | fail | the archive's (reference arm) | named none | — | 2026-09-16 09:19 |
2.0.2-9
|
amd64 | test | fail | the archive's (reference arm) | named none | — | 2026-09-16 09:19 |
2.0.2-9+py315.d.1
|
arm64 | build | pass | unknown | not read yet | — | 2026-09-16 10:03 |
2.0.2-9+py315.d.1
|
amd64 | build | pass | unknown | not read yet | — | 2026-09-16 09:57 |
2.0.2-9+py315.d.1
|
all | build | pass | unknown | not read yet | — | 2026-09-16 09:50 |