Description of problem: spacewalk/config/spacewalk-config.spec has %defattr(0644,root,root,0755) [...] %dir /etc/rhn backend/spacewalk-backend.spec has %define rhnconf %{_sysconfdir}/rhn [...] %attr(750,root,apache) %dir %{rhnconf} So depending on the order in which the packages are installed, the group of /etc/rhn can be either root or apache. The definitions should be the same. Ideally, only one package should probably own the directory. Version-Release number of selected component (if applicable): spacewalk-config-0.5.1-1 spacewalk-backend-0.5.1-1 How reproducible: Deterministic. Steps to Reproduce: 1. Look at the .spec's. Actual results: Different definitions. Expected results: Definitions the same, or directory owned by one package only. Additional info:
Made spacewalk-backend require spacewalk-config, removed dir ownership from spacewalk backend, changed mode & ownership in spacewalk-config to match what spacewalk-backend was doing (the latter appeared to win the depsolver war, and works on my spacewalk instance).
Dave, your fix made conflict in proxy. Since proxy require spacewalk-backend and spacewalk-proxy-common and spacewalk-proxy-common provide /etc/rhn and /etc/rhn/rhn.conf. I fixed it in commit 173c946197947e0f355c74078d02e734688d4623
Spacewalk 0.5 released.
*** Bug 500142 has been marked as a duplicate of this bug. ***
Spacewalk 0.5 has been released for long time ago.
Note to self -- Dave's commits were 9aa225a52c5d56b92f36ecfeb0201a04e273b075 and 835466a1fa00e2e328fb9adcaaa4df8f3602a7f9.
I am starting to see this issue in Spacewalk 1.8.
(In reply to comment #7) > I am starting to see this issue in Spacewalk 1.8. Please disregard. It was a configuration issue on my proxy server.