Shortcuts

/
focus the search box
Escape
leave the search, or close a menu or this
r
cycle the refresh interval
t
cycle the theme
?
this list

← Release team

pysph

1.0~b2-4 in the archive, ships a compiled extension

i
debci
graph
scan
states
sync
transition

Where it stands

built, ours is 1.0~b2-4+py315.1.

Nothing recorded is waiting on this one.

What was sent

published, 1.0~b2-4+py315.1, as work request 1274222.

Sent before this one: 1.0~b2-3+py315.2, 1.0~b2-3+py315.3. A version that was sent is spent, whatever came of it.

What is known

QuestionAnswerSaid byAs 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-traits 6.4.3-2+b3: not in our suite at all
python3-vtk9 9.6.2+dfsg1-5: we publish 9.6.2+dfsg1-4+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 'pysph.base.particle_array'
could not import meshio, pysph.base.box_sort_nnps, pysph.base.linked_list_nnps, pysph.base.nnps_base, pysph.base.particle_array, pysph.base.spatial_hash_nnps, pysph.parallel.parallel_manager 		deps/11 not dated
does the release team track this? dependency level 8
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 unknown, i386 unknown, loong64 unknown, ppc64el unknown, riscv64 unknown, s390x unknown
not in testing, so sid only 		release.debian.org, from their ben tracker 2026-09-16 04:49 UTC

Runs

VersionArchKindResultBinariesInterpretersClosureFinished
1.0~b2-4+py315.1 arm64 test pass rebuilt named none — 2026-09-15 04:40
1.0~b2-4+py315.1 amd64 test pass rebuilt named none — 2026-09-15 04:21
1.0~b2-4 arm64 test fail the archive's (reference arm) named none — 2026-09-15 03:29
1.0~b2-4 amd64 test fail the archive's (reference arm) named none — 2026-09-15 03:29
1.0~b2-4+py315.1 arm64 build pass unknown not read yet — 2026-09-15 04:37
1.0~b2-4+py315.1 amd64 build pass unknown not read yet — 2026-09-15 04:17
1.0~b2-4+py315.1 all build pass unknown not read yet — 2026-09-15 04:20
1.0~b2-3.1+py315.2 arm64 test pass rebuilt named none — 2026-09-12 16:32
1.0~b2-3.1+py315.2 amd64 test pass rebuilt named none — 2026-09-12 16:18
1.0~b2-3 arm64 test fail the archive's (reference arm) named none — 2026-09-12 15:26
1.0~b2-3 amd64 test fail the archive's (reference arm) named none — 2026-09-12 15:26
1.0~b2-3.1+py315.2 arm64 build pass unknown not read yet — 2026-09-12 16:30
1.0~b2-3.1+py315.2 amd64 build pass unknown not read yet — 2026-09-12 16:17
1.0~b2-3.1+py315.2 all build pass unknown not read yet — 2026-09-12 16:16
1.0~b2-3+py315.3 arm64 build fail unknown not read yet — 2026-09-06 21:12
1.0~b2-3+py315.3 amd64 build fail unknown not read yet — 2026-09-06 21:16
1.0~b2-3+py315.3 all build fail unknown not read yet — 2026-09-06 21:14
1.0~b2-3+py315.2 amd64 build fail unknown not read yet — 2026-09-02 09:11
1.0~b2-3+py315.2 all build fail unknown not read yet — 2026-09-02 09:11
1.0~b2-3 arm64 test fail the archive's (reference arm) named none — 2026-08-12 15:23
1.0~b2-3 amd64 test fail the archive's (reference arm) named none — 2026-08-12 15:23
1.0~b2-3+py315.1 amd64 build fail unknown not read yet — 2026-08-12 18:26