Description of problem: oddjob uses a default directory for dependent programs to store their "helpers". Depending on the architecture (and hence %{_libdir}), this directory is either /usr/lib/oddjob, or /usr/lib64/oddjob. I suspect these directories also have implications as to when SELinux is enforcing. The problem comes around when a noarch package tries to leverage oddjob. What directory should it use? A noarch package can't use %{_libdir} for file placement, as it may be inconsistent with %{_libdir} on the resulting system. e.g. a noarch package is built on a x86_64 system, so attempts to install into /usr/lib64/oddjob. A user then goes to install this noarch package on an i686 system... But /usr/lib64/oddjob is the wrong place on this system. Version-Release number of selected component (if applicable): Latest fc6 oddjob package. This bug appears to exist in fc5, fc6 and devel. Expected results: oddjob should have a single, consistent, architecture independent place for its users to store their helper scripts.
Another package can place its own helpers anywhere, really. Adding %{_libexecdir}/oddjob to the package for 0.29.