[Spacewalk-list] Upgrade to 2.5 fails when upgrading jabberd

[Daryl Rose]

>From the way that I read the instructions, I should be able to go from 2.3 to 2.5

  *   In most cases it's possible to perform Package upgrade and Schema upgrade steps from any previous version to the latest one directly (e.g. from 1.6 to 2.5). Make sure you have a valid backup in case anything will go wrong.

Thank you.

Daryl


________________________________
From: spacewalk-list-bounces at redhat.com <spacewalk-list-bounces at redhat.com> on behalf of Konstantin Raskoshnyi <konrasko at gmail.com>
Sent: Thursday, October 20, 2016 1:19 PM
To: spacewalk-list at redhat.com
Subject: Re: [Spacewalk-list] Upgrade to 2.5 fails when upgrading jabberd

As I remember you have to upgrade to 2.4 first

"These are upgrade instruction for upgrading Spacewalk 2.4 to Spacewalk 2.5"

https://fedorahosted.org/spacewalk/wiki/HowToUpgrade
HowToUpgrade - spacewalk - Fedora Hosted<https://fedorahosted.org/spacewalk/wiki/HowToUpgrade>
fedorahosted.org
Spacewalk Upgrade Instructions. These are upgrade instruction for upgrading Spacewalk 2.4 to Spacewalk 2.5 These upgrade instruction apply to Spacewalk installations ...




On Thu, Oct 20, 2016 at 11:00 AM, Daryl Rose <darylrose at outlook.com<mailto:darylrose at outlook.com>> wrote:

It was advised that I upgrade SW to 2.5 (I'm currently on 2.3).


I'm following the upgrade documentation, and one of the steps is to upgrade via yum.

  *   yum upgrade

I get to jabbered-2.4.0 and it fails with dependency issues.  Its looking for two PERL modules, Net::Jabber and Net::Jabber::XDB


Error: Package: jabberd-2.4.0-4.el6.x86_64 (epel)

           Requires: perl(Net::Jabber) >= 1.29

Error: Package: jabberd-2.4.0-4.el6.x86_64 (epel)

           Requires: perl(Net::Jabber::XDB)

 You could try using --skip-broken to work around the problem

 You could try running: rpm -Va --nofiles --nodigest


Both module are installed and work just fine, so I know this is error is a red herring.


My question is, if I use the --skip-broken, or rpm -Va --nofiles --nodigest, will that cause problems in the future, or cause problems with the upgrade?


Thank you


Daryl

_______________________________________________
Spacewalk-list mailing list
Spacewalk-list at redhat.com<mailto:Spacewalk-list at redhat.com>
https://www.redhat.com/mailman/listinfo/spacewalk-list

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://listman.redhat.com/archives/spacewalk-list/attachments/20161020/054f9823/attachment.htm>