Red Hat Bugzilla – Bug 450480
ejabberd upgrade to 2.0 causes ejabberd to not start
Last modified: 2008-07-02 06:06:33 EDT
The EPEL ejabberd version has recently been updated to 2.0 from 1.1. This broke both my installations, and they wouldn't start again till some love and attention to the config file (which is significantly different). http://fedoraproject.org/wiki/EPEL/GuidelinesAndPolicies says that major updates like this "should be avoided if possible at all." Probably too late now to do anything, so I'm not sure why I really filled this bug, but updates in EPEL should be less aggressive than fedora packages, as described in the policy link above. Was there some special reason for this update?
> 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.