Control: tags -1 confirmed
On 24/09/2025 19:05, Drew Parsons wrote:
Package: release.debian.org
Followup-For: Bug #004
openmpi is now stabilised and migrated to testing.
Ack. Go ahead.
Cheers,
Emilio
Control: tags -1 moreinfo
On 08/09/2025 18:42, Drew Parsons wrote:
Package: release.debian.org
Followup-For: Bug #004
I dug in a little further to follow up your point about cffi.
dolfinx (python3-dolfinx-real) catches the cffi abi but not nanobind.
As you mentioned, nanobind now (>= 2.8.0
Package: release.debian.org
Followup-For: Bug #004
Control: tags -1 - moreinfo
Fenics packages are updated and built in unstable.
As far as the fenics packages are concerned, they're ready for the
nanobind transition. openmpi is interfering with their migration to
testing however.
Package: release.debian.org
Followup-For: Bug #004
Emilio Pozuelo Monfort wrote:
> Unless I'm misunderstanding, the dependency should be in place (and in
> testing)
> before the transition starts, so that when nanobind is uploaded with the new
> ABI, britney will only migrate a set of packa
Hi Drew,
On Mon, 08 Sep 2025 18:42:08 +0200 Drew Parsons
wrote:
So, the fenics packages are ready for the nanobind transition (now
2.9.0).
We can upload the fenics patches before or after the nanobind
transition begins.
(uploading after would mean no binNMU would be needed)
I'll upload nan
Package: release.debian.org
Followup-For: Bug #004
I dug in a little further to follow up your point about cffi.
dolfinx (python3-dolfinx-real) catches the cffi abi but not nanobind.
As you mentioned, nanobind now (>= 2.8.0-1) has the same mechanism for
dh_python to add the abi dependency tha
Dear Release Team,
hi Timo,
FYI a transition of nanobind will require to rebuild fenics-basix too, in
addition to fenics-dolfinx.
Upstream FEniCS (which is the same for both libraries) may release a new
version of both towards the end of the summer, so it's good to rebuild the
version we have now
On 2025-08-13 23:53, Timo Röhling wrote:
Hi Drew,
* Drew Parsons [2025-08-13 16:43]:
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
Hi Drew,
* Drew Parsons [2025-08-13 16:43]:
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
On 2025-08-13 14:24, Timo Röhling wrote:
Package: release.debian.org
Severity: normal
X-Debbugs-Cc: nanob...@packages.debian.org, dpars...@debian.org,
balla...@debian.org
Control: affects -1 + src:nanobind
User: release.debian@packages.debian.org
Usertags: transition
-BEGIN PGP SIGNED
Package: release.debian.org
Severity: normal
X-Debbugs-Cc: nanob...@packages.debian.org, dpars...@debian.org,
balla...@debian.org
Control: affects -1 + src:nanobind
User: release.debian@packages.debian.org
Usertags: transition
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
Dear Release Team
11 matches
Mail list logo
