erich.neuwirth at univie.ac.at
Tue Mar 18 17:24:11 CET 2003
i am currently facing a problem.
i had to move a bunch of lists from an machine running
to another machine running 2.0.13
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
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.
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?
More information about the Mailman-Users