[Mailman-Users] Auto-approval patch
adam.nielsen at uq.edu.au
Thu Jun 3 04:55:05 CEST 2010
>> And I have now upgraded Mailman again to 2.1.13 and reapplied the
>> auto-approval patch, however I am not sure whether I need to do anything
>> with version numbers.
> The short answer is you need to run config_list with the
> "mlist.data_version = 96" input on only those lists which you created
> with Mailman 2.1.13 before you applied the patch. Probably this is no
> lists so you don't need to do anything.
> The long answer is the patch adds a new list attribute
> subscribe_auto_approval. Lists created without the patch do not have
> this attribute, and this will cause exceptions when the attribute is
> referenced by the patched code.
> Mailman has a mechanism for updating old list configurationson the fly
> and adding missing attributes and in cases like upgrading 2.0 to 2.1
> even refactoring old attributes into new ones. This mechanism is
> triggered by the list's data_version being less than the current
> schema. So setting the data_version of a list to 96 when the current
> schema is 97 will cause Mailman to invoke the versions.py updating
> process on the list the next time it is loaded.
> In your case, this will do no harm, but it isn't necessary unless you
> have a list or lists that were created without the patch and not
> previously updated.
Thanks for the detailed reply! I confirmed with grep (just to be safe)
that all the lists already had the subscribe_auto_approval value, so I
left them as is and so far all seems well. The UI picks up the value in
those fields so that's good.
Thanks again for the quick response!
More information about the Mailman-Users