Bug#1145118: adios4dolfinx: FTBFS for a different reason
Margarita Manterola
marga at debian.org
Sat Sep 12 17:39:40 BST 2026
Hi,
On 2026-09-12 15:18, Santiago Vila wrote:
> I confirm that the package fails to build for a different reason now.
> I've put a recent build log in the same directory as before:
> https://people.debian.org/~sanvila/build-logs/202608/
Right, those were the same errors that were seen in the Python 3.15
rebuild in debusine.
However, I've noticed that Francesco has uploaded a new version of
adios4dolfinx today and it failed to build with the same error as
reported in this bug:
https://buildd.debian.org/status/fetch.php?pkg=adios4dolfinx&arch=all&ver=0.11.0-2&stamp=1789226652&raw=0
@contextmanager
def ADIOSFile(
adios: adios2.ADIOS,
filename: Union[Path, str],
engine: str,
mode: adios2.Mode,
io_name: str,
comm: MPI.Intracomm | None = None,
):
io = adios.DeclareIO(io_name)
io.SetEngine(engine)
# ADIOS2 sometimes struggles with existing files/folders it
should overwrite
if mode == adios2.Mode.Write:
filename = Path(filename)
if filename.exists() and comm is not None and comm.rank ==
0:
if filename.is_dir():
shutil.rmtree(filename)
else:
filename.unlink()
if comm is not None:
comm.Barrier()
> file = io.Open(str(filename), mode)
^^^^^^^^^^^^^^^^^^^^^^^^^^^^
E ValueError: [1;36m[Sat Sep 12 15:23:54 2026][1;34m [ADIOS2
EXCEPTION][0m <Core> <IOHDF5> <MakeEngineHDF5> : A serial HDF5 engine
cannot be used with a communicator that is MPI-based.[0m
So, it seems that this error is still present, only somewhat flaky?
--
Regards,
Marga
More information about the debian-science-maintainers
mailing list