There is an issue with the list's data_version attribute vs.
Mailman.Version.DATA_FILE_VERSION. When the from_is_list and other new
attributes were added, Mailman.Version.DATA_FILE_VERSION was incremented to
make it greater than the list's data_version attribute which in turn will cause
the lists to be updated the first time they are instantiated.
Perhaps you had some other patches that incremented
Mailman.Version.DATA_FILE_VERSION, so that the list's data_version attribute was
not < Mailman.Version.DATA_FILE_VERSION causing the update to be skipped.
The way to fix this is to set Mailman.Version.DATA_FILE_VERSION to a value
greater than the data_version attribute of the lists.
First run this bash script
for l in `/path/to/mailman/bin/list_lists --bare`
do /path/to/mailman/bin/dumpdb /path/to/mailman/lists/$l/config.pck \
| grep data_version
done
This will print the data_version for each list. If N is the largest such value,
edit Mailman/Version.py to change the line
DATA_FILE_VERSION = 104
to set a value > N. Then visit the listinfo overview page which should update
all the lists.
Then so this doesn't happen again, set DATA_FILE_VERSION back to 104 in
Mailman/Version.py and create a file containing the single line
mlist.data_version = 104
and run this bash script
cd /path/to/mailman/bin/
for l in `./list_lists --bare`
do ./config_list -i /path/to/above/file $l
done
That should fix things.
The problem lists all have 98 as the data_version. Config_list does not work,
for input or output.
mjb.
------------------------------------------------------
Mailman-Users mailing list [email protected]
https://mail.python.org/mailman/listinfo/mailman-users
Mailman FAQ: http://wiki.list.org/x/AgA3
Security Policy: http://wiki.list.org/x/QIA9
Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/
Unsubscribe:
https://mail.python.org/mailman/options/mailman-users/archive%40jab.org
