On 31-07-2024 18:50, Sandro via devel wrote:
On 31-07-2024 17:34, Sandro Mani wrote:
See https://bugzilla.redhat.com/show_bug.cgi?id=2302033. The source of
the issue is that the Requires: environment(modules) in rpm-mpi-hooks
(which is a BuildRequirement of openmpi/mpich) did not result in
env
On 31-07-2024 17:34, Sandro Mani wrote:
See https://bugzilla.redhat.com/show_bug.cgi?id=2302033. The source of
the issue is that the Requires: environment(modules) in rpm-mpi-hooks
(which is a BuildRequirement of openmpi/mpich) did not result in
environment-modules getting installed, which brok
Hi
See https://bugzilla.redhat.com/show_bug.cgi?id=2302033. The source of
the issue is that the Requires: environment(modules) in rpm-mpi-hooks
(which is a BuildRequirement of openmpi/mpich) did not result in
environment-modules getting installed, which broke the dependency
generation by rpm-
Hi,
It seems something is going on with RPM metadata generation.
With the latest update of openmpi the generated metadata has changed:
$ rpm -q --provides -p openmpi-5.0.5-1.fc41.x86_64.rpm
config(openmpi) = 5.0.5-1.fc41
libmpi.so.40()(64bit)
libmpi_java.so.40()(64bit)
libmpi_mpifh.so.40()(64bi
