Just released mpich2-1.0.8-3 does not own some of its files. Here you go: [user@home ~]$ rpm -qf /usr/bin/mpi* file /usr/bin/mpicc is not owned by any package mpich2-1.0.8-3.fc10.x86_64 file /usr/bin/mpicxx is not owned by any package file /usr/bin/mpiexec is not owned by any package mpich2-1.0.8-3.fc10.x86_64 file /usr/bin/mpif77 is not owned by any package file /usr/bin/mpif90 is not owned by any package file /usr/bin/mpirun is not owned by any package mpich2-1.0.8-3.fc10.x86_64 These are the only links to executables not owned by a package in my /usr/bin. It is definitely not right. This directory is also orphaned: [user@home ~]$ rpm -qf /usr/share/mpich2/bin64 file /usr/share/mpich2/bin64 is not owned by any package Here is more but no one owns anything in /etc/alternatives/, so this may be okay: [user@home ~]$ rpm -qf /etc/alternatives/mpi* file /etc/alternatives/mpicc is not owned by any package file /etc/alternatives/mpicc-man is not owned by any package file /etc/alternatives/mpic++-man is not owned by any package file /etc/alternatives/mpicxx is not owned by any package file /etc/alternatives/mpi-exec is not owned by any package file /etc/alternatives/mpi-exec-man is not owned by any package file /etc/alternatives/mpif77 is not owned by any package file /etc/alternatives/mpif77-man is not owned by any package file /etc/alternatives/mpif90 is not owned by any package file /etc/alternatives/mpif90-man is not owned by any package file /etc/alternatives/mpi-run is not owned by any package At the end this is probably why this looks so strange: [user@home ~]$ rpm -q --whatprovides gcc mpicc gcc-4.3.2-7.x86_64 no package provides mpicc
(In reply to comment #0) ... > file /usr/bin/mpicc is not owned by any package > file /usr/bin/mpicxx is not owned by any package > file /usr/bin/mpiexec is not owned by any package > file /usr/bin/mpif77 is not owned by any package > file /usr/bin/mpif90 is not owned by any package > file /usr/bin/mpirun is not owned by any package > These and the /etc/alternatives/mpi* are files (links) created by the alternatives systems, and thus are really not rightfully owned by the mpich2 package(s). > These are the only links to executables not owned by a package in my /usr/bin. > It is definitely not right. This directory is also orphaned: > > [user@home ~]$ rpm -qf /usr/share/mpich2/bin64 > file /usr/share/mpich2/bin64 is not owned by any package > Will be fixed in mpich2-1.0.8-4.fc10 > > At the end this is probably why this looks so strange: > > [user@home ~]$ rpm -q --whatprovides gcc mpicc > gcc-4.3.2-7.x86_64 > no package provides mpicc Actually its not so strange ;), the package is mpich2, not mpicc. Thanks for the report.
mpich2-1.0.8-4.fc10 has been submitted as an update for Fedora 10. http://admin.fedoraproject.org/updates/mpich2-1.0.8-4.fc10
mpich2-1.0.8-4.fc10 has been pushed to the Fedora 10 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 mpich2'. You can provide feedback for this update here: http://admin.fedoraproject.org/updates/F10/FEDORA-2009-2875
mpich2-1.0.8p1-1.fc10 has been submitted as an update for Fedora 10. http://admin.fedoraproject.org/updates/mpich2-1.0.8p1-1.fc10
mpich2-1.0.8p1-1.fc9 has been submitted as an update for Fedora 9. http://admin.fedoraproject.org/updates/mpich2-1.0.8p1-1.fc9
Fixed in mpich2-1.0.8p1-2.fc10, Thanks.