Hi,
Have you done 'bin/update' after moving the backup config.pck file into the newly installed list directory ?
Alex Dupont wrote:
Hello,
I'm a "bit" in a loss here: I was running Mailman 2.1.2 on Debian 3.0 with no problems. Using apt-get... to upgrade Mailman to 2.1.4 produced an error. Well, besides the fact that all my archives got deleted (why would a script (!) do that??), I finally got Mailman back up and running version 2.1.4. I had to fix a zillion permissions, and it took me forever. Probably not a Mailman-thing, I know, and the package-maintainer isn't my friend, I can tell you that. But the following should be only Mailman-related:
(snip)
I think every packager should disclose their configure options so that upgrading can be done through our source distribution and the list dbs automatically updated !
-- Tokio Kikuchi, tkikuchi@ is.kochi-u.ac.jp http://weather.is.kochi-u.ac.jp/
------------------------------------------------------ Mailman-Users mailing list [EMAIL PROTECTED] http://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://www.python.org/cgi-bin/faqw-mm.py Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/
