Bug#1072183: fenics-dolfinx: FTBFS with nanobind 2.0
Francesco Ballarin
francesco.ballarin at unicatt.it
Thu Jun 6 11:51:02 BST 2024
Source: fenics-dolfinx
Version: 1:0.8.0-6
Followup-For: Bug #1072183
X-Debbugs-Cc: francesco.ballarin at unicatt.it, roehling at debian.org,
Hi Timo,
we are having issues making fenics-basix and fenics-dolfinx migrate to testing.
The issue is that the two downstream packages basix and dolfinx need to be
compiled with the same version of nanobind (so, 2.0+), but debci keeps picking
up pre-2.0 uploads when testing the other package.
Can you try adding the following Breaks to python3-nanobind
=========
Breaks: python3-basix (<< 0.8.0-3),
python3-dolfinx (<< 1:0.8.0-8)
python3-dolfinx-real (<< 1:0.8.0-8)
python3-dolfinx-complex (<< 1:0.8.0-8)
=========
Looking at https://tracker.debian.org/pkg/nanobind it is very much possible that
only the Breaks on python3-dolfinx is required to allow migration, but the other
three still look meaningful to us.
Thanks,
Francesco
-- System Information:
Debian Release: trixie/sid
APT prefers unstable
APT policy: (500, 'unstable')
Architecture: amd64 (x86_64)
Kernel: Linux 6.7.12-amd64 (SMP w/8 CPU threads; PREEMPT)
Locale: LANG=C, LC_CTYPE=C.UTF-8 (charmap=UTF-8), LANGUAGE not set
Shell: /bin/sh linked to /usr/bin/dash
Init: unable to detect
More information about the debian-science-maintainers
mailing list