Bug#1145118: adios4dolfinx: FTBFS for a different reason

[Margarita Manterola]

Hi,

I think that what may have happened here is that the failure that 
Santiago identified in his first message on August 22nd did actually go 
away with the rebuild, but then a second, unrelated failure started 
happening so that the rebuild on August 30th also failed.  Santiago, 
please correct me if that's not the case and you actually verified that 
the failure reason was the same.

The reason I'm saying this is that adios4dolfinx is failing to build in 
the reproducible builds infrastructure [1], but the log looks very 
different. There are tons of errors, one example:

     def test_read_write_P_2D(
         read_comm, family, degree, is_complex, mesh_2D, get_dtype, 
write_function, read_function
     ):
         mesh = mesh_2D
         f_dtype = get_dtype(mesh.geometry.x.dtype, is_complex)

         el = basix.ufl.element(
             family,
>           mesh.ufl_cell().cellname(),
             ^^^^^^^^^^^^^^^^^^^^^^^^^^
             degree,
             basix.LagrangeVariant.gll_warped,
             shape=(mesh.geometry.dim,),
             dtype=mesh.geometry.x.dtype,
         )
E       TypeError: 'str' object is not callable

Looking at the list of tests done by the reproducible builds 
infrastructure [2], we can see this successes and failures.

For experimental:
2026-08-16 06:17:00 	0.11.0-1exp1 	experimental 	amd64 	FTBFS
2026-08-05 02:18:00 	0.11.0-1exp1 	experimental 	amd64 	reproducible

For unstable:
2026-08-30 02:43:00 	0.10.0.post1-3 	unstable 	amd64 	FTBFS
2026-07-31 03:44:00 	0.10.0.post1-3 	unstable 	arm64 	reproducible

For forky:
2026-08-31 13:39:00 	0.10.0.post1-3 	forky 	amd64 	FTBFS
2026-08-03 17:18:00 	0.10.0.post1-3 	forky 	arm64 	reproducible

So, we don't know exactly when things broke, but some time in August 
there must have been a change that caused adios4dolfinx to stop 
building.

I suspected that this might be caused by fenics-dolphinx uploads, as the 
new 0.11 version was being uploaded to experimental during the window 
and to unstable also inside that window, but the failure in forky seems 
to disprove that, as the last migration to testing for fenics-dolphinx 
happened on 2026-07-29. Unless that failure is due to a different thing?

Indeed, the error seen forky (on August 31st) is the error that titles 
this bug [3]. So, perhaps it is the fact that the new fenics-dolphinx 
breaks adios4dolfinx, which requires a new upload, while something else 
broke something related to HDF5 temporarily, and while that's gone from 
unstable now, it's still happening in forky.

Regards,
Marga

[1]: 
https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/adios4dolfinx.html
[2]: 
https://tests.reproducible-builds.org/debian/history/adios4dolfinx.html
[3]: 
https://tests.reproducible-builds.org/debian/rb-pkg/forky/amd64/adios4dolfinx.html

-- 
Regards,
Marga