Description of problem: rpmlint /tmp/spacewalk-build/rpmbuild-spacewalk-config-git-9c870c5a6070590c6e8ce7909bb336270d213c52/noarch/spacewalk-config-0.5.6-1.git.9c870c5a6070590c6e8ce7909bb336270d213c52.noarch.rpm spacewalk-config.noarch: W: non-conffile-in-etc /etc/sysconfig/rhn-satellite-prep/etc/jabberd/s2s.xml spacewalk-config.noarch: W: non-conffile-in-etc /etc/sysconfig/rhn-satellite-prep/etc/jabberd/sm.xml spacewalk-config.noarch: W: non-conffile-in-etc /etc/sysconfig/rhn-satellite-prep/etc/jabberd/c2s.xml spacewalk-config.noarch: W: non-conffile-in-etc /etc/sysconfig/rhn-satellite-prep/etc/rhn/cluster.ini spacewalk-config.noarch: W: non-conffile-in-etc /etc/sysconfig/rhn-satellite-prep/etc/rhn/rhn.conf spacewalk-config.noarch: W: non-conffile-in-etc /etc/sysconfig/rhn-satellite-prep/etc/tomcat5/tomcat5.conf We do not want to mark this files as conffile since we *want* the to be replaced with package upgrade. So this files are not configuration files and should not be in /etc/ but rather somewhere in /usr as others templates. Version-Release number of selected component (if applicable): Spacewalk 0.5
Well, if we just use %config and not %config(noreplace), they will be replaced upon upgrade. Please complain if you disagree.
But if you put there pure %config, then you will get warning that you are using %config without (noreplace). I suppose it comes down to if: - those files are config files (which means user can configure them) and then this warning can be waived - it is not configuration files, but rather template, and it should not be in etc, but rather in /usr/share
Moving to space11.
Mass-moving to space13.
This has been solved as side effect of 491331. /etc/sysconfig/rhn-satellite-prep is now /var/lib/rhn/rhn-satellite-prep
Moving ON_QA ...
This bug has been fixed in Spacewalk 1.3.