F23 Self Contained Change: RPM MPI Requires Provides

[Dave Love]

Sandro Mani <manisandro at gmail.com> writes:

>>     Where are we with this?  I see some F23 builds but no updates yet.
>>
>>
>> Formally, this Change has been removed from the scope of F23 as it
>> was not ready for Alpha, which is a requirement to have a Change in
>> a release.
>> However Zbyszek told me yesterday that he is going to work on it and
>> would like to push this F23. So, lets see when it will be ready and
>> then decide whether it can still meet the F23.
>>
>> Regards,
>> Jan
> So the issues I pointed out in my previous mail (conerning
> MPI_PYTHON_SITEARCH and MPI_FORTRAN_MOD_DIR) above have been
> resolved. A batch of F24 rebuilts has been done by Zbyszek, hitting
> some build failures along the way. Most of these are now fixed, still
> needing a fix is nwchem which fails [1] due to what appears to be a
> fortran "use before decleared" issue. Once a full set of working F23
> package is built, the plan is to submit one big mass-update.

Should MPI packages be OK to push in f23 currently?  I've just had
failures from auto-qa like this, though the build actually ran an MPI
test successfully:

  not ok - depcheck for Koji build scalasca-2.2.2-2.fc23	# FAIL 
    ---
    arch: x86_64
    details:
      output: |-
        conflicting requests
        nothing provides libmpi.so.12()(64bit)(mpich-x86_64) needed by scalasca-mpich-2.2.2-2.fc23.x86_64
        nothing provides libmpicxx.so.12()(64bit)(mpich-x86_64) needed by scalasca-mpich-2.2.2-2.fc23.x86_64
        conflicting requests
        nothing provides libmpi.so.12()(64bit)(mpich-x86_64) needed by scalasca-mpich-2.2.2-2.fc23.x86_64
        nothing provides libmpicxx.so.12()(64bit)(mpich-x86_64) needed by scalasca-mpich-2.2.2-2.fc23.x86_64
        conflicting requests
        nothing provides libmpi.so.1()(64bit)(openmpi-x86_64) needed by scalasca-openmpi-2.2.2-2.fc23.x86_64
        nothing provides libmpi_cxx.so.1()(64bit)(openmpi-x86_64) needed by scalasca-openmpi-2.2.2-2.fc23.x86_64
  

> If anyone knowledgable of fortran has an idea how to fix the nwchem
> issue, that should resolve the last pending issue. Appears to have
> been triggered by a recent change of some other component, since it
> rebuilt fine just a few weeks back when testing in copr.
>
> Sandro
>
> [1] http://koji.fedoraproject.org/koji/buildinfo?buildID=676763

I can take a look if no-one else is going to.