[Systers-dev] Configuring Systers customization on dev.systers.org

Kathy Richardson kjr at casaveracruz.com
Fri May 14 16:19:50 PDT 2010


Hi Svaksha,

I chatted with Jen today, and learned a few things:
    The bzr checkout lp:systers is supposed to overwrite pieces in the 
Mailman directory.  Not create a sub directory of  the systers code.   I 
think the problem/typo in the instructions is that it needs to be a sudo 
command.
Jen typed it, and it clearly did a different install that the one we 
did, and the resulting installation made sense.  Now if you look at the 
/usr/local/mailman directory, you can tell what was updated and what 
wasn't by the lp:systers checkout.

I then edited the mm_cfg.py file.    I found that the .moved files are 
actually quite useful to see exactly what was changed.  I looked at the 
diff of mm_cfg.py and the mm_cfg.py.moved files to see what the 
configuration was for the running version of mailman and copied that 
over to the new config file.   Neither Jen nor I removed the .moved 
files.  Now I'm thinking that we should leave them so you can use them 
to understand the installation a bit more before we do the clean up.

Then restarted it again and the systers-admin stuff  now has the right 
dev.systers.org extensions on all the pages.

The password you gave me doesn't seem to work for creating new lists....

Talk later.  I might be a few minutes late, but will definitely be 
there.  I think Jen was also planning on being there.

-Kathy






Jennifer Redman wrote:
> On Thu, May 13, 2010 at 10:31 AM, स्वक्ष <vid at svaksha.com> wrote:
>
>   
>>     
>>> bzr checkout lp:systers .
>>>       
>> I used this command and it did checkout the stable repo. However, as
>> Jaideep said, the installation may have to be done manually (which I
>> dont want to mess up accidentally) as following the instructions on
>> the wiki didnt install dlists, essays UI, etc...
>>     
>
>
> I just successfully pulled the branch onto Systers - restarted everything
> and ran a check_perms.
>
> Here is what I did:
>
> # cd /usr/local/mailman
> # sudo bzr checkout lp:systers .
> # sudo /usr/local/bin/check_perms -f
>
> And at the end you'll see a bunch of conflicts - with the existing files
> moved to .moved. You can view the conflicts by typing:
>
> #bzr conflicts
>
> I think there is info in the instructions on how to get rid of all the moved
> files.
>
> You are going to want to just delete the systers directory off of
> /usr/local/mailman to help avoid confusion.
>
> Jen
>
>
> To unsubscribe from this conversation, send email to <systers-dev+customizatio+unsubscribe at systers.org> or visit <http://systers.org/mailman/options/systers-dev?override=117&preference=0>
> To contribute to this conversation, use your mailer's reply-all or reply-group command or send your message to systers-dev+customizatio at systers.org
> To start a new conversation, send email to <systers-dev+new at systers.org>
> To unsubscribe entirely from systers-dev, send email to <systers-dev-request at systers.org> with subject unsubscribe.


To contribute to this conversation, send mail to <Jennifer Redman >


More information about the Systers-dev mailing list