Bug 450480
Summary: | ejabberd upgrade to 2.0 causes ejabberd to not start | ||
---|---|---|---|
Product: | [Fedora] Fedora EPEL | Reporter: | Phil Anderson <pza> |
Component: | ejabberd | Assignee: | Peter Lemenkov <lemenkov> |
Status: | CLOSED CANTFIX | QA Contact: | Fedora Extras Quality Assurance <extras-qa> |
Severity: | low | Docs Contact: | |
Priority: | low | ||
Version: | el5 | CC: | silfreed |
Target Milestone: | --- | ||
Target Release: | --- | ||
Hardware: | All | ||
OS: | Linux | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | Bug Fix | |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2008-07-02 10:06:33 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
Phil Anderson
2008-06-09 00:38:11 UTC
> should be avoided if possible at all.
Should be, yes. But ejabberd 1.* lacks many necessary features (among them
file-proxy, in-band registration limitation, traffic shapers for gateways,
limitations on number of MUC--rooms user can join and so on).
I really sorry for your troubles, but IMHO updating to latest ejabberd worths
these efforts.
I disagree. The policy makes no allowances for features being so important that it is GUARANTEED to break all installations. There are lots of packages which have new versions out there with very useful new features that people would like, but aren't updated in CentOS or EPEL so as not to break installations. Maybe there should be (or maybe there is?) an alternative repository for things like this. Anyway, no point keeping this bug open. |