libuser

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

debci: 2026-09-16 04:49 UTC
graph: 2026-09-16 04:25 UTC
scan: 2026-09-16 21:00 UTC
states: 2026-09-16 20:18 UTC
sync: 2026-09-16 20:18 UTC
transition: 2026-09-16 04:49 UTC

Where it stands

pending, ours is 1:0.64+git20241106~dfsg-4+py315.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.1.

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

No run in this phase yet — it is pending.