https://bugzilla.redhat.com/show_bug.cgi?id=1337216
Randy Barlow <[email protected]> changed: What |Removed |Added ---------------------------------------------------------------------------- Component|ejabberd |erlang-p1_pam Summary|p1_pam fails to start - |p1_pam looks into |ejabberd barfs |ejabberd's install path to | |find epam instead of its | |own path --- Comment #4 from Randy Barlow <[email protected]> --- Hello Alan! I've written a patch that basically uses only the false clause of that case statement and tested it on my Rawhide box and now ejabberd does at least start. I'm going to make a new release of erlang-p1_pam with this patch for now, and then I'll file an upstream issue about this so we can get it solved in a more general way for everyone (not just Fedora). I agree that it's strange. Perhaps ejabberd itself is setting that variable, but I've honestly not done any investigation to determine where that is coming from. I did talk to Holger in the official ejabberd MUC and he confirmed that he had seen a similar issue. Thanks for the report, and I'll drop a link here when I report it upstream. Oh, and please feel free to let me know how your deployment goes! Jeremy Cline and I did a whole lot of work on ejabberd to upgrade to a recent version and split out the dependencies over the winter. It was much more work than we bargained for, so I hope it pays off well for our users! -- You are receiving this mail because: You are on the CC list for the bug. _______________________________________________ erlang mailing list [email protected] http://lists.fedoraproject.org/admin/lists/[email protected]
