Description of problem: Fedora Packaging says on their page https://fedoraproject.org/wiki/Packaging/SysVInitScript Packages with SysV-style initscripts must put any them into /etc/rc.d/init.d. A rpm macro exists for this directory, %_initrddir. In the past, some packages were putting files in /etc/init.d instead of /etc/rc.d/init.d. (/etc/init.d is a symlink to /etc/rc.d/init.d) This split made it more difficult to use yum install against the initscript filename and path. Since /etc/init.d is the symlink (and because the Filesystem Hierarchy Standard does not mandate a location), Fedora requires that all SysV-style initscripts must go into the full /etc/rc.d/init.d directory. The package spacewalk-proxy-tools states the location of rhn-proxy initscript is /etc/init.d/rhn-proxy. Version-Release number of selected component (if applicable): spacewalk-proxy-tools-0.4.5-1.el5 How reproducible: Deterministic. Steps to Reproduce: 1. rpm -ql spacewalk-proxy-tools | grep '/etc' Actual results: /etc/init.d/rhn-proxy Expected results: /etc/rc.d/init.d/rhn-proxy Additional info: Well, maybe the rhn-proxy should be gone from /etc/*/init.d altogether and moved to /usr/sbin, just like rhn-satellite was moved away from /etc.
Fixed in 487e805f549d3a3dc0022769958588848af09253 and in packages: spacewalk-proxy-installer-0.5.1-1 spacewalk-proxy-0.5.1-1
Spacewalk 0.5 released.
Spacewalk 0.5 has been released for long time ago.