Hi,
> 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 ejab
On 2008-12-03 01:10, Helmut Grohne wrote:
> 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 t
On Wed, Dec 03, 2008 at 01:10:38AM +0100, Helmut Grohne wrote:
> 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 :
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. I
therefore suggest adding some notes on ejabberd to the release notes. It
should basically tell:
1) Back up /var/lib/ejab
4 matches
Mail list logo
