9.5-6 in the archive, ships a compiled extension
build failed,
ours is 9.5-6+py315.2,
waiting on cypari2, matplotlib, python-psutil, rpy2, scipy.
python3-dev-only
build-depend on python3-all-dev instead of python3-dev
Rebuilding it releases 1 package waiting on it, as this stage last counted.
aborted,
9.5-6+py315.2,
as work request 1204376,
which ended in work request 1204378.
Which turned out to be build-failed: the workflow ended: build-failed, work request 1204378.
Sent before this one:
9.5-6+py315.1.
A version that was sent is spent, whatever came of it.
| Question | Answer | Said by | As of |
|---|---|---|---|
| Why did the build fail? |
unsatisfiable-in-sid
a build dependency nothing in Debian satisfies, so the package is unbuildable for anybody: an RC bug this transition merely noticed |
deps/11 | not dated |
| 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 |
| Version | Arch | Kind | Result | Binaries | Interpreters | Closure | Finished |
|---|---|---|---|---|---|---|---|
9.5-6+py315.2
|
arm64 | build | fail | unknown | not read yet | — | 2026-09-06 16:15 |
9.5-6+py315.2
|
amd64 | build | fail | unknown | not read yet | — | 2026-09-06 16:22 |
9.5-6+py315.2
|
all | build | fail | unknown | not read yet | — | 2026-09-06 16:21 |
9.5-6+py315.2
|
arm64 | build | fail | unknown | not read yet | — | 2026-08-31 20:42 |
9.5-6+py315.2
|
amd64 | build | fail | unknown | not read yet | — | 2026-08-31 20:43 |
9.5-6+py315.2
|
all | build | fail | unknown | not read yet | — | 2026-08-31 20:42 |
9.5-6+py315.1
|
all | build | fail | unknown | not read yet | — | 2026-08-20 07:49 |