On 2025-10-08 07:33, Paul Gevers wrote:
Hi, On 10/7/25 22:19, Drew Parsons wrote:The problem is that with the fenics packages, the different components use each other.So, wouldn't it be better to test these three packages together.Dependency on the virtual package, python3-nanobind-abi16, is intended to fix the situation, and is the change that has been made in unstable that I am trying to migrate.So if I understand you correctly, the changes in unstable are exactly to prevent the current situation in the future. Good.
...
There are two more solutions (of which I prefer 1 as it's seems technically correct, I assume you'd prefer 2): 1) the involved packages (python3-basix if I'm right) carry a Breaks (on python3-dolfinx if I'm right) for the lifetime of forky to ensure users also don't do partial upgrades (and then the migration software will run the tests with all those binaries from unstable)2) we manually trigger the tests with the three packages from unstable
I can apply option 1) if it's your preferred solution.(I was trying to avoid adding extra conditions debian/control, but as you point at it can help prevent partial upgrades)
Drew