cvc5

1.3.2-1 in the archive, ships a compiled extension

Where it stands

built, ours is 1.3.2-1+py315.2.
python3-dev-only
build-depend on python3-all-dev instead of python3-dev

Nothing recorded is waiting on this one.

published, 1.3.2-1+py315.2, as work request 1216212.

Question	Answer	Said by	As of
Why did the build fail?	superseded-dependency Built against our own rebuild of a dependency, one generation back. The run is evidence, unlike an archive copy: re-run it against the current suite before reading the failure. cython3 3.1.6+dfsg-3+py315.1: we publish 3.1.6+dfsg-3.1+py315.1	deps/11	not dated
was the interpreter under test installed?	no its chroot had a different Python installed instead, so its failure is about whatever that one is: these take their interpreter from the default rather than from pybuild python3.14_3.14.6-1	the build log's installed set	not dated

Version	Arch	Kind	Result	Binaries	Interpreters	Closure	Finished
`1.3.2-1+py315.2`	arm64	test	pass	rebuilt	named none	—	2026-09-02 13:51
`1.3.2-1+py315.2`	amd64	test	pass	rebuilt	named none	—	2026-09-02 14:10
`1.3.2-1`	arm64	test	pass	the archive's (reference arm)	named none	—	2026-09-02 09:35
`1.3.2-1`	amd64	test	pass	the archive's (reference arm)	named none	—	2026-09-02 09:35
`1.3.2-1+py315.2`	arm64	build	pass	unknown	not read yet	—	2026-09-02 13:49
`1.3.2-1+py315.2`	amd64	build	pass	unknown	not read yet	—	2026-09-02 14:07
`1.3.2-1`	arm64	test	fail	the archive's (reference arm)	named none	—	2026-08-02 21:08
`1.3.2-1`	amd64	test	fail	the archive's (reference arm)	named none	—	2026-08-02 21:08
`1.1.2-2+py315.1`	arm64	build	fail	unknown	not read yet	—	2026-08-03 00:15
`1.1.2-2+py315.1`	amd64	build	fail	unknown	not read yet	—	2026-08-03 01:35