Hello Jan-Albert,

The only version of jabberd that I can find is 2.4.0-4.  I do not see 2.4.0-2 
anywhere, including in the test repository.  If you could please post a link to 
where I can download version 2.4.0-4, I would appricate it.


Thank you.


Daryl


________________________________
From: spacewalk-list-boun...@redhat.com <spacewalk-list-boun...@redhat.com> on 
behalf of Ree, Jan-Albert van <j.a.v....@marin.nl>
Sent: Monday, October 24, 2016 6:50 AM
To: spacewalk-list@redhat.com
Subject: Re: [Spacewalk-list] Upgrade to 2.5 fails when upgrading jabberd


At the time I wrote this at least my local EPEL mirror still had 2.4.0-2 as 
latest, right now it also has 2.4.0-4

I installed a test spacewalk-nightly VM 2 weeks ago and there I did not run 
into any issues using the regular EPEL, thus my suggestion.

Besides : EPEL-testing sometimes carries stuff you don't want to run in 
production yet, it's stability isn't guaranteerd like with the normal EPEL.

--

Jan-Albert van Ree


Jan-Albert van Ree | Linux System Administrator | MARIN Support Group
MARIN | T +31 317 49 35 48 | j.a.v....@marin.nl<mailto:j.a.v....@marin.nl> | 
www.marin.nl<http://www.marin.nl>

[LinkedIn]<https://www.linkedin.com/company/marin> [YouTube] 
<http://www.youtube.com/marinmultimedia>  [Twitter] 
<https://twitter.com/MARIN_nieuws>  [Facebook] 
<https://www.facebook.com/marin.wageningen>
MARIN news: 
www.opendagbijmarin.nl<http://www.marin.nl/web/News/News-items/www.opendagbijmarin.nl.htm>

________________________________
From: spacewalk-list-boun...@redhat.com <spacewalk-list-boun...@redhat.com> on 
behalf of Daryl Rose <darylr...@outlook.com>
Sent: Friday, October 21, 2016 16:45
To: spacewalk-list@redhat.com
Subject: Re: [Spacewalk-list] Upgrade to 2.5 fails when upgrading jabberd


Jan-Albert,


When you say "epel stable", I'm assuming that you mean the regular epel 
repository, http://download.fedoraproject.org/pub/epel/6/$basearch


I only see jabberd 2.4.0-4 in this repository.

I commented out jabberd testing as you suggest, but this did not make any 
difference.  So when I review the contents of the repository, I could only find 
2.4.0-4.

Thank you.

Daryl

________________________________
From: spacewalk-list-boun...@redhat.com <spacewalk-list-boun...@redhat.com> on 
behalf of Ree, Jan-Albert van <j.a.v....@marin.nl>
Sent: Thursday, October 20, 2016 3:07 PM
To: spacewalk-list@redhat.com
Subject: Re: [Spacewalk-list] Upgrade to 2.5 fails when upgrading jabberd


Disable EPEL testing and only use EPEL stable and retry (this has 
jabberd-2.4.0-2 instead of 2.4.0-4)

There might be a bug in the newer EPEL-testing package

--

Jan-Albert


Jan-Albert van Ree | Linux System Administrator | MARIN Support Group
MARIN | T +31 317 49 35 48 | j.a.v....@marin.nl<mailto:j.a.v....@marin.nl> | 
www.marin.nl<http://www.marin.nl>

[LinkedIn]<https://www.linkedin.com/company/marin> [YouTube] 
<http://www.youtube.com/marinmultimedia>  [Twitter] 
<https://twitter.com/MARIN_nieuws>  [Facebook] 
<https://www.facebook.com/marin.wageningen>
MARIN news: MARIN at SNAME in Washington, November 
1-5<http://www.marin.nl/web/News/News-items/MARIN-at-SNAME-in-Washington-November-15.htm>

________________________________
From: spacewalk-list-boun...@redhat.com <spacewalk-list-boun...@redhat.com> on 
behalf of Daryl Rose <darylr...@outlook.com>
Sent: Thursday, October 20, 2016 20:00
To: spacewalk-list@redhat.com
Subject: [Spacewalk-list] Upgrade to 2.5 fails when upgrading jabberd


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@redhat.com
https://www.redhat.com/mailman/listinfo/spacewalk-list

Reply via email to