25.9.1-2 in the archive, ships a compiled extension
built,
ours is 25.9.1-3+py315.1,
waiting on python-greenlet, python-psutil.
ahead of the archive (built from a source sid does not have)
Rebuilding it releases 1 package waiting on it, as this stage last counted.
published,
25.9.1-2+py315.1,
as work request 1014181,
which ended in work request 1014200.
Which turned out to be tests-aborted: the tests were stopped: work request 1014200.
| Question | Answer | Said by | As of |
|---|---|---|---|
| Why did the build fail? |
archive-dependency
Built against the archive's copy of a dependency we have rebuilt. The ordering has not reached it, so this is not the package's own fault. python3-cffi-backend 2.0.0-3+py315.1: we publish 2.1.1-1+py315.1 python3-charset-normalizer 3.4.7-2: we publish 3.4.7-2+py315.1 python3-greenlet 3.3.2-4: we publish 3.3.2-4+py315.1 python3-zope.interface 8.5-3+py315.1: we publish 8.6-1+py315.1 |
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 'gevent.resolver.cares' could not import _xxsubinterpreters, gevent.libuv, gevent.resolver.cares, test, test.ssl_servers, test.test_httpservers |
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 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 |
| 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 #1144998 python-gevent: FTBFS building against python 3.15 |
the BTS usertag | not dated |
| Version | Arch | Kind | Result | Binaries | Interpreters | Closure | Finished |
|---|---|---|---|---|---|---|---|
25.9.1-3+py315.1
|
arm64 | test | pass | rebuilt | named none | — | 2026-08-20 08:37 |
25.9.1-3+py315.1
|
amd64 | test | pass | rebuilt | named none | — | 2026-08-20 08:37 |
25.9.1-3+py315.1
|
arm64 | build | pass | unknown | not read yet | — | 2026-08-20 08:36 |
25.9.1-3+py315.1
|
amd64 | build | pass | unknown | not read yet | — | 2026-08-20 08:36 |
25.9.1-3+py315.1
|
all | build | pass | unknown | not read yet | — | 2026-08-20 08:35 |
25.9.1-2+py315.1
|
arm64 | build | fail | unknown | not read yet | — | 2026-08-16 13:36 |
25.9.1-2+py315.1
|
amd64 | build | fail | unknown | not read yet | — | 2026-08-16 13:37 |
25.9.1-2+py315.1
|
all | build | fail | unknown | not read yet | — | 2026-08-16 13:38 |