The mailing list for listmasters using Sympa

[Marco Gaiarin <address@concealed>]

Mandi! "Simone Dal Maso" (via sympa-users Mailing List)
  In chel di` si favelave...

> How do you fix the problem in your sympa.conf?

I've restored sympa.conf from backups, then fixed by hand the debconf
database (because i was afraid that a full 'dpkg-reconfigure -plow sympa'
would brake something other...) to prevent future modification.

Also, because sympa started with the ''wrong'' domain, some tasks get
created and after fixing sympa.conf, sympa complain about. So i've also
cleaned up task spool dir (/var/spool/sympa/task/).
There's also some DB cleanup, but i think it is fully optional (eg: some
data get duplicated on another domain, but clearly never used).


> Because now if I make apt-get upgrade, I lost all. What I don't know is 
> if during the upgrade process, sympa.conf is the unique file that will 
> be modified, because if the problem is only one file, I can backup it 
> and restore manually.

Of course. I've a doubt about wwsympa.conf also...


> Anyway, for me it is a bug, I'm quite sure to write to debian mantainer 
> to inform them.

I think the same. At least, sympa have to inform user that modify
'sympa.conf', or at least provide a backup copy (.dpkg-old or .ucf-old).

If you fire up the bug, please say me (or the list). Thanks.

-- 
  Against software patents:
  http://www.freepatents.org - http://no-patents.prosa.it