Description of problem: Why remove -devel and -libs sub-packages? Guidelines state that files for development only should go into a -devel package: https://fedoraproject.org/wiki/Packaging:Guidelines#Devel_Packages At the very least it is usual to do: Obsoletes: %{name}-devel < %{version}-%{release} Provides: %{name}-devel = %{version}-%{release} See https://fedoraproject.org/wiki/PackagingDrafts/ProvidesObsoletes when dropping sub-packages. I see that this has not been pushed as an update yet, but I ran into it trying to compile paraview which has a BR (properly I think) on openmpi-devel. Version-Release number of selected component (if applicable): openmpi-1.3.1-2.fc11.x86_64
Yes, please provide at least openmpi-devel, since otherwise one needs more conditionals in spec files (at the moment there is already one for mpi-selector in RHEL and another for environment-modules in newer Fedoras). Also, please fix #476844 before pushing the update.
This bug appears to have been reported against 'rawhide' during the Fedora 11 development cycle. Changing version to '11'. More information and reason for this action is here: http://fedoraproject.org/wiki/BugZappers/HouseKeeping
I'll probably add the -devel back (or else make a psuedo provides for the -devel package). The libs don't need separated out because they are intrinsically tied to the runtime. You could link against the libs, but without the runtime, they don't provide a functional MPI interface (such as there are no MPI ranks available, etc). You could also do without the -devel package under normal conditions, but at least for the openmpi-1.3.2 update that I'm preparing, the -devel package will be required as openmpi-1.3.2 is binary incompatible with all previous versions meaning all openmpi linked apps will have to be recompiled. In the future that won't be the case and the -devel package would truly be optional.
*** Bug 511532 has been marked as a duplicate of this bug. ***
(In reply to comment #3) > I'll probably add the -devel back (or else make a psuedo provides for the > -devel package). The libs don't need separated out because they are > intrinsically tied to the runtime. You could link against the libs, but > without the runtime, they don't provide a functional MPI interface (such as > there are no MPI ranks available, etc). You could also do without the -devel > package under normal conditions, but at least for the openmpi-1.3.2 update that > I'm preparing, the -devel package will be required as openmpi-1.3.2 is binary > incompatible with all previous versions meaning all openmpi linked apps will > have to be recompiled. In the future that won't be the case and the -devel > package would truly be optional. Okay. OpenMPI 1.3.3 has been released, could you update to that? I see you have removed the -devel and -libs packages in the cvs branch of F-11, but haven't touched the rawhide branch..
I've restored the -devel package (but not the -libs package as the libs are not really useful without the runtime anyway). Resolved in openmpi-1.3.3-1
openmpi-1.3.3-1.fc11 has been submitted as an update for Fedora 11. http://admin.fedoraproject.org/updates/openmpi-1.3.3-1.fc11
openmpi-1.3.3-2.fc11 has been pushed to the Fedora 11 testing repository. If problems still persist, please make note of it in this bug report. If you want to test the update, you can install it with su -c 'yum --enablerepo=updates-testing update openmpi'. You can provide feedback for this update here: http://admin.fedoraproject.org/updates/F11/FEDORA-2009-7951
Unfortunately a new update was pushed which omitted adding this bug to a new update to supercede the one above. Please visit: https://admin.fedoraproject.org/updates/F11/FEDORA-2009-10848 and test the version in updates-testing before it gets pushed to stable (which will happen very soon) to make sure there are no regressions.