Re: [sympa-fr] migration 3.4.3 vesr

[Olivier Salaün - CRU <adresse@cachée>]

Tu peux migrer directement en 5.0.

La liste des incompatibilités est listée dans le fichier NEWS de la 
distribution, préfixés par '*****'. Ces incompatibilités te seront 
d'ailleurs rappellées au début du "make install". Dans ton cas, tu auras 
une liste assez longue, voir le fichier ci-joint.

Si tu utilises Mysql, tous les changements de structure de la base 
devraient s'effectuer automatiquement au premier démarage de sympa.pl.
Autre gros changement, le nouveau format de templates. Au premier 
démarage, sympa.pl tentera une migration automatique des anciens.
Si tu authentifies tes utilisateurs avec LDAP, attention, le format du 
fichier auth.conf a changé.

Bref tout devrait bien se passer...

adresse@cachée wrote:

> Je travaille actuellement sur la remise au carré de notre serveur sympa.
> Je vais en profiter pour le mettre à jour.
> Nous utilisons une vielle version : 3.4.3, et apparement il y a eu pas mal de 
> modif depuis.
>
> Est-il possible de migrer directement en 5.0, ou faut-il d'abord migrer en 
> 4.x ?
> Y a t'il un moyen d'exporter le contenu du serveur en 3.4.3, pour l'injecter 
> dans un autre serveur en 5.0 ?
> Est-que quelqu'un aurait un retour d'expérience ?
>  

You are upgrading from Sympa 3.4.3
You should read CAREFULLY the changes listed below ; they might be 
uncompatible changes :
<RETURN>

*****   require new perlmodule XML-LibXML

*****   You should update your DB structure (automatically performed by Sympa 
with MySQL), adding the following table (mySQL example) :
*****   CREATE TABLE admin_table (
*****   list_admin              varchar(50) NOT NULL,
*****   user_admin              varchar(100) NOT NULL,
*****   role_admin              enum('listmaster','owner','editor') NOT NULL,
*****   date_admin              datetime NOT NULL,
*****   update_admin            datetime,
*****   reception_admin         varchar(20),
*****   comment_admin           varchar(150),
*****   subscribed_admin        enum('0','1'),
*****   included_admin          enum('0','1'),
*****   include_sources_admin   varchar(50),
*****   info_admin              varchar(150),
*****   profile_admin           enum('privileged','normal'),
*****   PRIMARY KEY (list_admin, user_admin,role_admin),
*****   INDEX (list_admin, user_admin,role_admin)
*****   );

*****   Extend the generic_sso feature ; Sympa is now able to retrieve the 
user email address in a LDAP directory

*****   We have both changed Sympa's template format and catalogue format
*****
*****   Template file format is now TT2 (hhtp://www.tt2.org). Its format is 
similar
*****   to the old template format. Sympa.pl should detect that you are 
upgrading
*****   from an old version and will run the tpl2tt2.pl script to migrate your
*****   existing .tpl files to .tt2 format.
*****
*****   We now use PO format for Sympa internationalization. This is a much 
more
*****   standard format which make it easier for translators to update 
catalogues.
*****   Because we could not automatically extract translatable strings from 
templates
*****   most of the translation job is to be done again and only 3 languages 
are supported
*****   with this release (the one that have uptodate PO files)
*****   If you are concerned about translating Sympa, please read this 
document :
*****   http://www.sympa.org/howtotranslate.html

*****   The 'msgcat' sympa.conf parameter is now obsolete. You should set the 
'locaeldir'
*****   parameter instead.

*****   src/List.pm: Changed default for 'user_data_source' ('file' => 
'include2')

*****   Change 'cas' entries format in auth.conf :
*****           host            => base_url
*****           login_uri       => login_path
*****           check_uri       => service_validate_path
*****           logout_uri      => logout_path

*****   New 'attributes_user' field in the 'subscriber_table'
*****   If you are using MySQL, Sympa.pl will change the database structure
*****   at startup. If using Pg, Oracle or Sybase you should ALTER the table
*****   structure according to the provided create_db.x scripts.

*****   auth.conf format has changed ; if you had a previous auth.conf file 
you
*****   should change it according to the new format
*****   To keep the existing authentication bahovior you should add the 
following entries at the
*****   end of your existing auth.conf file :
*****               user_table
*****               regexp                 .*

*****   You should update your database structure based on the create_db.xxx 
scripts
*****   unless you are using MySQL (Sympa tries to update the database 
automatically at startup)

***** 'port' parameter no more supported in include_ldap_query paragraphs

***** If you are upgrading from a previous Sympa version, you should update
***** your sympa DB as  follows :
***** ALTER TABLE subscriber_table CHANGE date_subscriber timestamp with time 
zone NOT NULL;
***** ALTER TABLE subscriber_table CHANGE update_subscriber timestamp with 
time zone;

Attachment: smime.p7s
Description: S/MIME Cryptographic Signature