Re: [Jabberd2] can't log in: upgrading from 216 to 2110

Tomasz Sterna wrote: >> > ERROR: invalid byte sequence for encoding "UTF8": 0xe05107 >> > ERROR: invalid byte sequence for encoding "UTF8": 0xe05107 > > Do you have your database created with -E UNICODE encoding? this, from the pgdump file ... > CREATE DATABASE [...] ENCODING = 'UTF8'; utf

Re: [Jabberd2] can't log in: upgrading from 216 to 2110

Dnia 26-07-2007, czw o godzinie 13:03 -0700, Jad Shipman napisał(a): > and once I redid the vCard table (wow! a lot more > columns! when did that happen?) With the 2.1.0 release. :-) It's explained in the UPGRADE file. > Except the postgresql log grows when I would try to connect, by two > lin

[Jabberd2] jabberd-2.1.11 release

It's time for another jabberd 2.1 series release. Get 2.1.11 release as usual at: http://ftp.xiaoka.com/jabberd2/releases/jabberd-2.1.11.tar.gz http://ftp.xiaoka.com/jabberd2/releases/jabberd-2.1.11.tar.bz2 and read: http://svn.xiaoka.com/jabberd2/trunk/UPGRADE There are only bug and compliance

[Jabberd2] can't log in: upgrading from 216 to 2110

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 I have a working 2.1.6 installation, but thought it best to keep up with the upgrades, and so have tried to move to the latest, 2.1.10; it compiles fine, and once I redid the vCard table (wow! a lot more columns! when did that happen?) nothing crashed.