[Systers-dev] GSoC Bug Fixes and Mailman setup in Ubuntu 9.10
kanika vats
kanika.krikan at gmail.com
Sat Mar 27 21:31:02 PDT 2010
Hmm,
I now remember we used migrate_old_list only during testing period to make
the Systers Mailman lists compatible with the new changes.I never looked at
the migrate_old_lists code though.When priya said:
"In fact, instead of labelling it as a bug, it can be
a wishlist item as there is already an alternate solution to it albeit
a bit less user friendly (using the migrate script)."
I thought maybe that script covers for making the original Mailman list
compatible as well.Even I used to delete all the lists that were created by
original Mailman code.Sorry for the confusion guyz.Anna,thanks for the
clarification ;>
On Sun, Mar 28, 2010 at 9:49 AM, kanika vats <kanika.krikan at gmail.com>wrote:
>
> I agree with Anna
>
> On Sun, Mar 28, 2010 at 3:56 AM, Anna Granudd <anna.granudd at gmail.com>wrote:
>
>> Hi,
>>
>> Also the migrate script does not seem to be creating
>> > any database for existing lists.
>> >
>> >
>> It shouldn't.
>> Just for everyones information - you don't need to use the migrate script
>> if
>> you install everything now. It was created last year after a few
>> additional
>> attributes had been added to the Mailman list object and these attributes
>> were not set for the "old" lists on the production server (such as this
>> one,
>> systers-dev) which would make the system crash. Hence, we needed to set
>> them
>> which was done using the migrate script. If you set up your system now,
>> these new attributes will be set for all your lists and you don't need to
>> worry about it.
>>
>> As for lists created with "normal" Mailman - I don't think these were ever
>> compatible with the code after adding the Systers code (please correct me
>> if
>> I'm wrong). At least, I always deleted mine and created new ones after
>> adding Systers' modifications. There are more changes than just those
>> fixed
>> with the migrate script (such as an additional database for the dynamic
>> lists, which you noted). This makes it necessary (or at least a lot
>> easier)
>> to recreate your lists after adding Systers' changes.
>>
>> Thanks,
>> Anna
>>
>>
>> To unsubscribe from this conversation, send email to <
>> systers-dev+mailman7+unsubscribe at systers.org<systers-dev%2Bmailman7%2Bunsubscribe at systers.org>>
>> or visit <
>> http://systers.org/mailman/options/systers-dev?override=80&preference=0>
>> To contribute to this conversation, use your mailer's reply-all or
>> reply-group command or send your message to
>> systers-dev+mailman7 at systers.org <systers-dev%2Bmailman7 at systers.org>
>> To start a new conversation, send email to <systers-dev+new at systers.org<systers-dev%2Bnew at systers.org>
>> >
>> To unsubscribe entirely from systers-dev, send email to <
>> systers-dev-request at systers.org> with subject unsubscribe.
>>
>
>
>
> --
> Best Regards
> Kanika Vats
>
--
Best Regards
Kanika Vats
To contribute to this conversation, send mail to <Anna Granudd >
More information about the Systers-dev
mailing list