libuser

1:0.64+git20241106~dfsg-4 in the archive, ships a compiled extension

bugs: 2026-10-07 00:45 UTC
debci: 2026-10-06 04:49 UTC
graph: 2026-10-06 04:25 UTC
scan: 2026-10-07 03:00 UTC
states: 2026-10-07 03:18 UTC
sync: 2026-10-07 03:18 UTC
transition: 2026-10-06 04:49 UTC

Where it stands

tests failed, ours is 1:0.64+git20241106~dfsg-4+py315.d.1.
no-interpreter-build-dependency
add python3-all-dev; the headers currently arrive indirectly, from the default interpreter

Nothing recorded is waiting on this one.

What was sent

published, 1:0.64+git20241106~dfsg-4+py315.d.1, as work request 1305747.

What is known

Question	Answer	Said by	As of
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

Runs

Version	Arch	Kind	Result	Binaries	Interpreters	Closure	Finished
`1:0.64+git20241106~dfsg-4+py315.d.1`	arm64	test	fail	rebuilt	named none	—	2026-09-18 18:48
`1:0.64+git20241106~dfsg-4+py315.d.1`	amd64	test	fail	rebuilt	named none	—	2026-09-18 18:55
`1:0.64+git20241106~dfsg-4`	arm64	test	fail	the archive's (reference arm)	named none	—	2026-09-18 15:10
`1:0.64+git20241106~dfsg-4`	amd64	test	fail	the archive's (reference arm)	named none	—	2026-09-18 15:10
`1:0.64+git20241106~dfsg-4+py315.d.1`	arm64	build	pass	unknown	not read yet	—	2026-09-18 18:47
`1:0.64+git20241106~dfsg-4+py315.d.1`	amd64	build	pass	unknown	not read yet	—	2026-09-18 18:50