On Tue, 21 Nov 2006, Sergei Golovan wrote:
Change between 1.1.2-2 and 1.1.2-3 didn't touch LDAP support at all.
Well, that is odd then
Could you upgrade only ejabberd to 1.1.2-3 (and erlang-base and
erlang-nox to 1:11.b.2-1 as well)?
I didn't notice erlang being upgraded, but it is indeed at 11.b.2-1
Just to make sure that it's not erlang/ejabberd fault
(after that the bug may be closed or reassigned).
I've not yet had my first cup of coffee, so I'll blame this on just
getting up and not being up to snuff... but I'm not sure what you
are asking.
it seems like I have shown:
* erlang* 11.b.2-1 and ejabberd 1.1.2-2 work
* erlang* 11.b.2-1 and ejabberd 1.1.2-3 fail
however, I do have a non-server machine I can replicate the database
to for testing (I've forgotten how to create a db dump, will have to
look that up again) All machines are current as of yesterday.
just let me know combinations you would like to see tested.
Thanks,
--
Rick Nelson
<darkangel> I generally don't use anything that has "experimental" and
"warning" pasted all over it
<darkangel> no, I'm not that dumb... hehe
<Knghtbrd> ...
* darkangel considers downloading the latest unstable kernel
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
