The mailing list for listmasters using Sympa

[David Verdin <address@concealed>]

That's almost the way to go !
You also need to change the etc/data_structure.version content to make 
it match the version of your previous Sympa (5.2.3 for you) in order to 
make Sympa know that it must upgrade.
Well... that's how you should do it if you installed from the source.
I didn't here of any particular precaution to take on debian 
distributions but I thought that upgrading from a package to another 
would also update the database, file encondings, perform the upgrade in 
other words.
You should contact the debian package users list to have more 
informations: http://packages.debian.org/lenny/sympa

Regards,

David

Marco Gaiarin a écrit :
> I'm planning a migration of one of my main server, from debian etch to
> debian lenny, and from one hardware to another.
>
> I've just migrated a server from etch to lenny (from sympa
> 5.2.3-1.2+etch1 to 5.3.4-6.1), and sympa got upgraded
> flawlessy 'in place'.
>
> But... how to handle migration in this situation? Reading around 
>
>         http://www.sympa.org/manual/upgrading
>
> seems that i have to:
>
> 1) install new sympa package in new hardware, keep it unconfigured (or
>  do basic and dumb configuration).
>
> 2) stop old sympa server, backup all data (conf, list archives,
>  databases, ...)
>
> 3) unpack data on new server, restore database
>
> 4) tackle some minimal configuration options (database connect strings,
>  ...) as needed.
>
> 5) start sympa -upgrade on new hardware, leave sympa itself to do the upgrade
>  on first startup.
>
>
> Right? Some more precaution to take for debian packages?
>
>
> Thanks.
>
>   

--
David Verdin
Comité réseau des universités