[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#1111004: transition: nanobind



On 2025-08-13 14:24, Timo Röhling wrote:
Package: release.debian.org
Severity: normal
X-Debbugs-Cc: nanobind@packages.debian.org, dparsons@debian.org, ballarin@debian.org
Control: affects -1 + src:nanobind
User: release.debian.org@packages.debian.org
Usertags: transition

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA512

Dear Release Team,

I'd like to transition the nanobind package after an ABI bump, which
requires a rebuild of at least fenics-dolfinx as it exposes the nanobind
ABI.

Ben file:

title = "nanobind";
is_affected = .depends ~ /\bpython3-nanobind\b/ | .depends ~ /\bpython3-nanobind-abi[0-9]+\b/ | .provides ~ /\bpython3-nanobind-abi[0-9]+\b/; is_good = .depends ~ /\bpython3-nanobind-abi16\b/ | .provides ~ /\bpython3-nanobind-abi16\b/; is_bad = .depends ~ /bpython3-nanobind-abi15\b/ | .provides ~ /\bpython3-nanobind-abi15\b/;


Thanks for this Timo. nanobind 2.8 is also needed for scipy 1.16 support.

I suspect the entire fenicsx stack will need rebuilding.
This python3-nanobind-abi is not being used as a Dependency by the needing packages.
Is there a way to get it declared?

Dependencies on the numpy abi are generated by dh_numpy3, activated by dh-sequence-numpy3. Should we create a dh_nanobind tool (with dh-sequence-nanobind) for the client packages to use?
That would help streamline these nanobind transitions.

Drew


Reply to: