Currently in Spacewalk we build and ship our own version of jabberd (jabberd-2.0).
EPEL-5 testing currently contains jabberd-2.2.5-1, which does following in its %post: ... #create ssl certificate cd /etc/jabberd if [ ! -e server.pem ]; then /bin/sh /etc/pki/tls/certs/make-dummy-cert server.pem /bin/chown root.jabber server.pem /bin/chmod 640 server.pem fi So the new jabberd generates /etc/jabberd/server.pem which will conflict with certificate generated by rhn-ssl-tool (spacewalk-certs-tools) and the installation fails. Not a problem now, but it'll become an issue once the new jabberd hits EPEL-5. Any idea how to deal with this? -Milan _______________________________________________ Spacewalk-devel mailing list [email protected] https://www.redhat.com/mailman/listinfo/spacewalk-devel
