Hi,
I just borked my public jabber server by upgrading to the latest snapshot.
I was running 4.3 with ejabberd but in 4.4 the ejabberd version is
upgraded to 2.0.
In the README.OpenBSD there is a mention of this upgrade:
"* Migration
When moving database between machines, or upgrading from 1.1.x
2008/8/15 Wijnand Wiersma <[EMAIL PROTECTED]>:
[cut]
> I think it is working for me now again, except for ejabberdctl. If I
> figure this out and it has something to do with the strange way of
> upgrading I had to perform now I will notify you guys.
Ok, it was still totally borked.
I had to make s
On Fri, Aug 15, 2008 at 01:22:45PM +0200, Wijnand Wiersma wrote:
> 2008/8/15 Wijnand Wiersma <[EMAIL PROTECTED]>:
> Maybe there should be a warning for upgrading users before they start?
> Just like the postgresql upgrades in releases.
Thank you for reminding me, I've already contacted appropriat
viq schreef:
> On Fri, Aug 15, 2008 at 01:22:45PM +0200, Wijnand Wiersma wrote:
>
>> 2008/8/15 Wijnand Wiersma <[EMAIL PROTECTED]>:
>>
>
>
>> Maybe there should be a warning for upgrading users before they start?
>> Just like the postgresql upgrades in releases.
>>
>
> Thank you for
