-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On Wed, 4 Mar 2009 15:28:59 +0100 Milan Zazrivec <mzazri...@redhat.com> wrote:
> 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 > Spacewalk-devel@redhat.com > https://www.redhat.com/mailman/listinfo/spacewalk-devel Additionally we're not building our own jabberd in F10 devel repos, rather using the one in Fedora, which is causing a nasty crash: https://bugzilla.redhat.com/show_bug.cgi?id=487618 This is with 2.2.4-1.fc10. Possible we could be have the same problem on el5 once this package enters EPEL. :( Devan - -- Devan Goodwin <dgood...@redhat.com> Software Engineer Spacewalk / RHN Satellite Halifax, Canada 650.567.9039x79267 -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.9 (GNU/Linux) iEYEARECAAYFAkmulhgACgkQAyHWaPV9my5nqACfQ6FTRnpV+3XAvi/Pshithbir IG0An1FyAsYCPgVoyU4es0jSZHfRCYzL =ppXd -----END PGP SIGNATURE----- _______________________________________________ Spacewalk-devel mailing list Spacewalk-devel@redhat.com https://www.redhat.com/mailman/listinfo/spacewalk-devel
