Bug 638840 - Update jabberd in EPEL?
Summary: Update jabberd in EPEL?
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Fedora EPEL
Classification: Fedora
Component: jabberd
Version: el5
Hardware: All
OS: Linux
low
low
Target Milestone: ---
Assignee: Dominic Hopf
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard: UpdatePackage
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2010-09-30 06:07 UTC by Ben Carner
Modified: 2010-10-27 19:10 UTC (History)
3 users (show)

Fixed In Version: jabberd-2.2.11-1.el5
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2010-10-27 19:10:01 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)

Description Ben Carner 2010-09-30 06:07:40 UTC
Description of problem:
Is jabberd 2 (Not eJabberd) supported in EPEL anymore?

Version-Release number of selected component (if applicable):
2.2.8-2
2.2.11

How reproducible:
Always

Is Jabberd supported in EPEL anymore? I haven't seen any updates since 2.2.8 and I notice 2.2.11 has been released upstream with "Major bugfixes in XML parsing and connection handling." That to me sounds like a worth-while upgrade but would be problematic if no one is handling this anymore.

Comment 1 Adrian Reber 2010-09-30 06:41:47 UTC
Yes it is. dmaphy (on CC) just recently updated it on rawhide. The reason why I never updated it (on any branch and EPEL) is that the versions are not always 100% upgradable. At least it was that way in the past. Therefore, as there have been no security bugs, I never wanted to update it.

Maybe dmaphy is a bit more adventurous ;-)

Comment 2 Dominic Hopf 2010-09-30 22:34:42 UTC
Well, we did not get any feedback from Rawhide users, yet. So not sure if I should go ahead and build it for at least F14 and F13 now?

I think at least a manual review of the configuration files will be necessary, would such an update fit EPEL requirements? I actually am not sure about that, would be the first time I'm pushing an update to EPEL. ;)

I really would like to if there are no complaints about that. :)

Comment 3 Mark Chappell 2010-10-01 17:38:40 UTC
Dominic,

*If* there are no changes to defaults and it happily reads the old config files you should be fine.  You may also want to take a look and see if the plugin architecture is compatible, in case people have created their own plugins.

Comment 4 Dominic Hopf 2010-10-01 19:42:36 UTC
Well, current configuration from 2.2.8 should run fine with 2.2.11 as far as I was able to test that. New configuration files are created as *.rpmnew, thus this point actually should be fine I think.

I'll check out what about the plugin architecture is, but I think it's likely that the API/ABI at least is compatible if it even changed.

Once I made that sure, I'll go ahead an push that update. Assigning this bug to me. :)

Comment 5 Dominic Hopf 2010-10-07 00:03:10 UTC
Just pushed the updates for F14 and F13. While doing that I pointed out some building issues with EPEL, so the update here takes a bit longer. Sorry for the inconvenience.

Comment 6 Fedora Update System 2010-10-10 15:13:46 UTC
jabberd-2.2.11-1.el5 has been submitted as an update for Fedora EPEL 5.
https://admin.fedoraproject.org/updates/jabberd-2.2.11-1.el5

Comment 7 Dominic Hopf 2010-10-10 15:14:42 UTC
Feel free to give feedback and Karma on this update. :)

Comment 8 Fedora Update System 2010-10-10 18:01:42 UTC
jabberd-2.2.11-1.el5 has been pushed to the Fedora EPEL 5 testing repository.  If problems still persist, please make note of it in this bug report.
 If you want to test the update, you can install it with 
 su -c 'yum --enablerepo=updates-testing update jabberd'.  You can provide feedback for this update here: https://admin.fedoraproject.org/updates/jabberd-2.2.11-1.el5

Comment 9 Fedora Update System 2010-10-27 19:09:56 UTC
jabberd-2.2.11-1.el5 has been pushed to the Fedora EPEL 5 stable repository.  If problems still persist, please make note of it in this bug report.


Note You need to log in before you can comment on or make changes to this bug.