On Friday 27 March 2009 14:30:07 Devan Goodwin wrote: > 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?
To be able to do yum upgrade, we need to resolve that file conflict, so I guess we're gonna have to uninstall rhn-org-httpd-ssl-key-pair first and run yum upgrade afterwards. We should be able to restore previous ssl certificates after the upgrade somehow (we probably don't want to generate new key pair), though I cannot think of any nice & straightforward way how to accomplish that (only thing I can think of is to reconstruct the original rhn-org.rpm with server.pem in new location). Anybody has any other idea how to solve this? -Milan _______________________________________________ Spacewalk-devel mailing list [email protected] https://www.redhat.com/mailman/listinfo/spacewalk-devel
