[Systers-dev] bin/newlist cannot be used to create a new list from the command line [bug]

[स्वक्ष]

Hello All,

On Wed, Jun 2, 2010 at 15:22, Anna Granudd <anna.granudd at gmail.com> wrote:
> Hi,
> I answered Svaksha in private (well, of the comment she left in the bug and
> not the email but still) but she asked me to post my comment to the
> systers-dev list instead so everybody could read it so here it comes.

Thanks Anna :)

> I checked out the script and it was never under version control and hence
> can never have worked for normal use from that we introduced dlists (since
> when we did this we also started needing to create a db for each dlist,
> choose if we wanted a dlist or non dlist etc.). Since I was assigned to the
> bug I thought it might be enough to just add the missing attributes I added
> last year to Mailman/Cgi/create.py (what I did last year was to add
> fullname_required, essay_enabled and the possibility to set the questions
> for the essay to this file, the dlist related code is older) but since we
> never used the script apart for the things listed by Kathy and Terri (as of
> my knowledge) we'd also need to add all the dlist stuff including creating
> db's for new dlists. Basically we'd need to check that everything done in
> the UI (and this can be found in the earlier mentioned file) is also done in
> this newlist script or possibly a new script which creates new lists for
> Systers, to not interfere with what the regular Mailman code might need. So,
> I'd say this was not something part of last years GSoC but an older bug we
> never discovered before.

Umm... I am still new to Systers so please bear with me while I try to
understand how the systers stable branch interfaces with MM. When Anna
had mentioned that this was an older bug, I'd remembered that systers
was working closely with MM to push in some nice useful features,
imho, like 'unsubscribing from individual threads', etc...

Since this bug (in systers-stable) does not allow the sysadmin to
create new lists via the CLI, its possible that upstream (mailman
3.0?) may hesitate pulling systers customizations unless the bug is
resolved. I am guessing this based on the fact that an MM default
installation allows the list creation via CLI and CGI/GUI.

I was taking help from one of the MM devels who was mentioning
reverting to an unpatched version. So if this bug in the systers
stable branch changes the way a default MM functions (which I am not
sure how it does exactly although Anna has explained some of it) I
wonder how upstream would accept the changes. This is my limited
understanding of the bug and I may be totally wrong about this as Jen,
Robin or Terri would know more about Syster customizations.

</thinking out loud>

The above is why I had asked all the folks who had a successful
installation of the syster-stable branch to reply with their
individual experiences. If you were able to use the CLI to create a
newlist please holler --that means I can close the bug (and I
apologise for wasting people's time) as it only occurred on my
installation. If you are able to reproduce the error then its really a
bug. So please take a few minutes to check this and give feedback,
either here or on LP as a comment.

> Svaksha - as you notice this is only part of what I wrote to you and
> slightly modified, feel free to add what else I might have said if you think
> it's relevant. Oh, and I (which you probably figured by now) only ever used
> the CGI to create new lists.

Anna, can you please try via the cli and report on the bug (basically
confirm if its a bug or not). If, as you say this is a really old bug,
its just that I am a little surprised that it was not caught before.

Thanks for reading.

-- 
thanks and regards,
vid || http://svaksha.com