Re: [Spacewalk-devel] Installation problems on the horizon (when jabberd-2.2.5 hits EPEL)
On Monday 09 March 2009 09:59:23 Jan Pazdziora wrote: > On Sun, Mar 08, 2009 at 11:17:29AM +0100, Milan Zazrivec wrote: > > > > 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? > > > > > > Why will it conflict with certificate generated by > > > spacewalk-certs-tools? That package does not own > > > /etc/jabberd/server.pem, does it? > > > > Both packages own that certificate file. > > I'm probably missing something: > > $ rpm -qlp spacewalk-certs-tools-0.5.2-1.el5.noarch.rpm | grep > server.pem > | wc -l 0 /etc/jabberd/server.pem is owned by the package created by rhn-ssl-tool, (i.e. rhn-org-httpd-ssl-key-pair-`hostname` package). -Milan ___ Spacewalk-devel mailing list Spacewalk-devel@redhat.com https://www.redhat.com/mailman/listinfo/spacewalk-devel
Re: [Spacewalk-devel] Installation problems on the horizon (when jabberd-2.2.5 hits EPEL)
On Sun, Mar 08, 2009 at 11:17:29AM +0100, Milan Zazrivec wrote: > > > > > > 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? > > > > Why will it conflict with certificate generated by > > spacewalk-certs-tools? That package does not own > > /etc/jabberd/server.pem, does it? > > Both packages own that certificate file. I'm probably missing something: $ rpm -qlp spacewalk-certs-tools-0.5.2-1.el5.noarch.rpm | grep server.pem | wc -l 0 $ -- Jan Pazdziora Satellite Engineering, Red Hat ___ Spacewalk-devel mailing list Spacewalk-devel@redhat.com https://www.redhat.com/mailman/listinfo/spacewalk-devel
Re: [Spacewalk-devel] Installation problems on the horizon (when jabberd-2.2.5 hits EPEL)
On Saturday 07 March 2009 20:13:49 Jan Pazdziora wrote: > On Wed, Mar 04, 2009 at 03:28:59PM +0100, Milan Zazrivec 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? > > Why will it conflict with certificate generated by > spacewalk-certs-tools? That package does not own > /etc/jabberd/server.pem, does it? Both packages own that certificate file. -Milan ___ Spacewalk-devel mailing list Spacewalk-devel@redhat.com https://www.redhat.com/mailman/listinfo/spacewalk-devel
Re: [Spacewalk-devel] Installation problems on the horizon (when jabberd-2.2.5 hits EPEL)
On Wed, Mar 04, 2009 at 03:28:59PM +0100, Milan Zazrivec 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? Why will it conflict with certificate generated by spacewalk-certs-tools? That package does not own /etc/jabberd/server.pem, does it? -- Jan Pazdziora Satellite Engineering, Red Hat ___ Spacewalk-devel mailing list Spacewalk-devel@redhat.com https://www.redhat.com/mailman/listinfo/spacewalk-devel
Re: [Spacewalk-devel] Installation problems on the horizon (when jabberd-2.2.5 hits EPEL)
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On Wed, 4 Mar 2009 15:28:59 +0100 Milan Zazrivec 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 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
[Spacewalk-devel] Installation problems on the horizon (when jabberd-2.2.5 hits EPEL)
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
