i had to move a bunch of lists from an machine running 2.0.5 to another machine running 2.0.13
applying bin/move_list i managed.
now i wanted to upgrade to 2.1.1 on the new machine and this failed.
the problem seems to be that the upgrade reads some information from config.pck and not from config.db for the lists. after the attemped upgrade the lists suddenly know about the old machine again. but just running it in 2.0.13 is fine.
i used bin/config_list -i newurl ... for the lists, and this did not solve the problem.
is there a way of enforcing a sync between config.pck and config.db?
i do not pretend to understand the architecture. but i am surprised that it works in 2.0.13 and then not in 2.1.1
is there an easy fix?
------------------------------------------------------ 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/
This message was sent to: [EMAIL PROTECTED] Unsubscribe or change your options at http://mail.python.org/mailman/options/mailman-users/archive%40jab.org
