Package: ejabberd Version: 2.0.1-5 Severity: important Technically this report does really apply to 2.0.1-5~bpo40+1 but I think them to be close enough. So feel free to close this report if you think that it is inappropriate.
I tried upgrading ejabberd 1.1.2-6 to 2.0.1-5~bpo40+1 (which should be almost the same version as that to be released with lenny) on my etch/i386 system and this really failed. First thing before trying this: Back up /var/lib/ejabberd now. After backing up I tried to upgrade which failed, because the config file syntax changed. I therefore suggest that ejabberd is not started again if upgrading from 1.1.2-6. After fixing the configuration file I was still unable to start ejabberd. It runs an epmd and another process, but doesn't open the desired tcp ports. I have not yet tried to start ejabberd with a clean /var/lib/ejabberd. However these failures are enough for me to conclude that the upgrade is not straight forward at all and should be documented and assisted by the debian package. I'll also file a bug against release-notes to mention ejabberd as a difficult package. Helmut -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
