-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On Fri, 27 Mar 2009 13:40:25 +0100 Milan Zazrivec <[email protected]> wrote:
> Of course, when upgrading from earlier version of Spacewalk to 0.5, > hitting this problem is pretty much unavoidable: your > rhn-org-https-ssl-key-pair from previous installation owns > /etc/jabberd/server.pem which is also owned by jabberd-2.2.5-1 > (the new version of jabberd that yum upgrade tries to upgrade to) > and the whole yum upgrade fails (that said, Spacewalk 0.5 is not > upgradeable at the moment). > > -Milan Anything we can do or is that basically going to require a manual step? Thanks, Devan - -- Devan Goodwin <[email protected]> Software Engineer Spacewalk / RHN Satellite Halifax, Canada 650.567.9039x79267 -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.9 (GNU/Linux) iEYEARECAAYFAknM1OIACgkQAyHWaPV9my6GTQCfcauD5aEW4duSfm8y6obRQhcO O1gAoKEgEoej2G1kasEhC8mGFi6YYKEE =s0gg -----END PGP SIGNATURE----- _______________________________________________ Spacewalk-devel mailing list [email protected] https://www.redhat.com/mailman/listinfo/spacewalk-devel
