[Systers-dev] Additional Development Server

[स्वक्ष]

Hi Gloria and other list members,

I'm vidya and have been more active on the irc channel that the list.
I'll sent a complete introduction soon. For now I wanted to post my
notes regarding virtualenv and pip just incase any other potential
gsoc student like me wants to try it.
Fwiw, I've tried installing VirtualBox (including the packaged ose)
but they simply crash after installing on Ubuntu9.10 powered by Amd.
On irc I was pointed to a bug,
https://bugs.launchpad.net/ubuntu/+source/virtualbox-ose/+bug/347487


On Wed, Mar 31, 2010 at 07:25, Gloria W <strangest at comcast.net> wrote:
>>
>> I found this blog post and all of these tools sound awesome:
>> http://clemesha.org/blog/2009/jul/05/modern-python-hacker-tools-virtualenv-fabric-pip/
>>
>> Virtualenv, fabric and pip.
>>
>> As long as we can have controlled deviation from testing and prod -- I
>> think it would be really great to get some more "real" python development
>> tools into the mix.  Thanks Gloria for the suggestions and being willing to
>> help get set up!
>>
> Sure. Fabric is more of a deployment tool, running commands on remote
> machines via Python. Pip is a better easy_install, which allows un-install
> (which must be done manually using easy_install/setuptools), and perfroms
> error checking before installation (so it is less likely to fail during
> installation). I think the handiest tools for our immediate need are
> virtualenvwrapper/virtualenv. If we are also trying to resolve repackaging
> and repeated deployment issues, the others are handy as well.

I had already installed and was using virtualenv for some other python
projects and tried installing MM by this method. Everything worked
great till I came to the part where we:
1.  Correct any permission problems and
$ sudo su
$ cd /usr/local/mailman
$ bin/check_perms
$ bin/check_perms -f
2. Secure the Archives as root on
http://systers.org/systers-dev/doku.php/step_by_step_system_installation
$ sudo su
$ cd /usr/local/mailman/archives
$ chown www-data private
$ chmod o-x private
$ exit

That killed my virtualenv as I see this error when i try to create a
temporary work enviroinment:
bash: /home/mom/virtualenvwrapper-1.26/virtualenvwrapper_bashrc: No
such file or directory

I am not sure why the virtualenv was affected and would like to know
what mistake I made and if I am missing a step or procedure. Now I am
reinstalling virtualenv and maybe will try the same (Correct any
permission problems and Secure the Archives) within this environment.
I'll keep the list posted on my progress.

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