Bug 638840
| Summary: | Update jabberd in EPEL? | ||
|---|---|---|---|
| Product: | [Fedora] Fedora EPEL | Reporter: | Ben Carner <kwalker> |
| Component: | jabberd | Assignee: | Dominic Hopf <dmaphy> |
| Status: | CLOSED ERRATA | QA Contact: | Fedora Extras Quality Assurance <extras-qa> |
| Severity: | low | Docs Contact: | |
| Priority: | low | ||
| Version: | el5 | CC: | adrian, dmaphy, tremble |
| Target Milestone: | --- | ||
| Target Release: | --- | ||
| Hardware: | All | ||
| OS: | Linux | ||
| Whiteboard: | UpdatePackage | ||
| Fixed In Version: | jabberd-2.2.11-1.el5 | Doc Type: | Bug Fix |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2010-10-27 19:10:01 UTC | Type: | --- |
| Regression: | --- | Mount Type: | --- |
| Documentation: | --- | CRM: | |
| Verified Versions: | Category: | --- | |
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
| Cloudforms Team: | --- | Target Upstream Version: | |
| Embargoed: | |||
|
Description
Ben Carner
2010-09-30 06:07:40 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 ;-) 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. :) 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. 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. :) 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. 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 Feel free to give feedback and Karma on this update. :) 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 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. |