Bug#507616: release-notes: ejabberd is a difficult to upgrade package
Helmut Grohne
Severity: normal
I recently tried to upgrade ejabberd to backports (which has almost the
same version as that to be released with lenny) and it failed. I
therefore suggest adding some notes on ejabberd to the release notes. It
should basically tell:
1) Back up /var/lib/ejabberd *before* upgrading.
2) The syntax of the configuration file changed, so it must be updated
by hand.
3) The upgraded ejabberd may be unable to start up (for unknown
reasons).
A separate bug is reported against ejabberd.
Helmut
--
To UNSUBSCRIBE, email to debian-bugs-...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listm...@lists.debian.org
Simon Paillard
> Package: release-notes
> Severity: normal
>
> I recently tried to upgrade ejabberd to backports (which has almost the
> same version as that to be released with lenny) and it failed.
Did you notice the maintainer question for you :
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=507615#10 ?
> A separate bug is reported against ejabberd.
#507615
--
Simon Paillard
W. Martin Borgert
> 1) Back up /var/lib/ejabberd *before* upgrading.
> 2) The syntax of the configuration file changed, so it must be updated
> by hand.
> 3) The upgraded ejabberd may be unable to start up (for unknown
> reasons).
>From the bug report it's not clear to me, whether ejabberd has
really an upgrade problem or not. If this is realle the case, I
will put your text into the release notes, OK?
Helmut Grohne
> From the bug report it's not clear to me, whether ejabberd has
> really an upgrade problem or not. If this is realle the case, I
> will put your text into the release notes, OK?
Partly yes:
> 1) Back up /var/lib/ejabberd *before* upgrading.
This is the directory contains all data for ejabberd. Therefore it is
always a good idea to do a backup. ;-) Secondly the database format has
changed and ejabberd will migrate tables to the new format. As a result
it is not possible to downgrade again if you run into trouble with the
new ejabberd.
> 2) The syntax of the configuration file changed, so it must be updated
> by hand.
Most users will have adapted their configuration file. They will have
defined server admins for instance. Keeping the old configuration file
will result in a wrong configuration of ejabberd as some configuration
itmes changed their name.
> 3) The upgraded ejabberd may be unable to start up (for unknown
> reasons).
I was unable to further investigate this issue due to lack of time. I
was asked to try this by upgrading to lenny, but that would have
required me setting up a dedicated machine. There has been an upload
fixing the issue, but it seemed to fix pubsub table migration. As I
don't use pubsub I believe (but can of course not prove) that the
problem will still affect at least some users.
Hope this helps.
Helmut