[Systers-dev] GSoC Bug Fixes and Mailman setup in Ubuntu 9.10

[priya iyer]

Hello,

On Sat, Mar 27, 2010 at 6:18 PM, kanika vats <kanika.krikan at gmail.com> wrote:
> Hi Priya,
>
> Yes,you have migrate_old_lists script to take care of that.Since solution is
> available it is definitely not a bug.You can have your idea in the wishlist
> though.
>
> What I think is that it is good to have a feature in the web interface only
> if it is used quite often or every time a particular action needs to be
> triggered.If a person uses Systers Mailman code from the very beginning then
> he/she will face no such problem but if that person used the original
> Mailman code first to create lists and then plans to switch to Systers
> Mailman then he or she will need to run migrate_old_lists only once after
> integrating Systers code,as later on all other lists are provided with an
> option in the user interface to whether have the Dlist feature enabled or
> not.

Understood :). That's why I was wondering if it should just be called
a wishlist item. But I have been experimenting with Syster's mailman
for past several hours and I have a few more observations regarding
this matter.

Before migrating to Syster's mailman I had created around 3 lists.
After the migration, I created the required Systers-Admin mailing list
via the command line. All was good. I could send emails, tinker with
admin settings and so on. But I realised I could not subscribe even in
the mailing lists created _after_ adding Syster's mailman code. I
finally realised that if I make a list via the command line it doesn't
have the Syster's modifications.

Only the new lists created via the web will have those attributes
(fullname_required etc.). I realised this when I was browsing the
PostgreSQL database using PgAdmin3 to learn how the data is stored
(for solving the essay bug #296181 [1] and would need this knowledge
for the archival project as well). I could not see any database with a
mailing list name even after migrating the old lists. After creating
another list via the web interface I saw a database with the list name
appear in PgAdmin that had all the required tables.

So I guess the command line 'newlist' tool does not create a
compatible list. Also the migrate script does not seem to be creating
any database for existing lists.

> I think we should mention about the 'migrate script' in step by step system
> installation at Systers wiki so that other people dont face similar
> problems.

I would like to try and add this. I haven't checked yet to see if the
wiki needs approved  membership or not. Will do it as soon as am done
with some more exploration. :)

Regards
Priya Kuber (beachbrake)

1] Bug https://bugs.launchpad.net/systers/+bug/296181