Description of problem: It looks like the mpich2 package is owning the /usr/bin/mpiexec file which is actually an alternatives target. I think that this is not the indented way of packaging tools with alternatives support as if more than one packages do so, a conflict between them is created. Version-Release number of selected component (if applicable): mpich2-1.2.1p1-1, it seems that in koji there is a successful build for 1.4.1p1 but this is in trashcan. This version removes alternative support according to the changelog. (I hope that it doesn't own this file as the name is too generic to be owned by a specific package). How reproducible: Every time Steps to Reproduce: # rpm -qf /usr/bin/mpiexec Actual results: mpich2-1.2.1p1-1.el5 Expected results: file /usr/bin/mpiexec is not owned by any package like the case of java keytool which supports alternatives: # rpm -qf /usr/bin/keytool file /usr/bin/keytool is not owned by any package Additional info: none
Ooops i just found out that "%ghost" is used in files section of .spec. For some reason i believed that %ghost files doesn't appear in rpm -qf output. Closing this ticket as a won't fix. Sorry for the inconvenience this may have caused.