broken virtualenv pip install

[david415]

I think it reasonable to pip install python programs inside a python virtualenv... don't you?

Here's some output from the failure... others should be able to reproduce this:

byte-compiling /home/deploy/virtenv/lib/python2.7/site-packages/exaproxy/reactor/content/init.py to init.pyc

byte-compiling /home/deploy/virtenv/lib/python2.7/site-packages/exaproxy/reactor/redirector/worker.py to worker.pyc

byte-compiling /home/deploy/virtenv/lib/python2.7/site-packages/exaproxy/reactor/redirector/manager.py to manager.pyc

byte-compiling /home/deploy/virtenv/lib/python2.7/site-packages/exaproxy/reactor/redirector/init.py to init.pyc

byte-compiling /home/deploy/virtenv/lib/python2.7/site-packages/exaproxy/application.py to application.pyc

running install_data

creating /usr/lib/systemd

error: could not create '/usr/lib/systemd': Permission denied

---

Cleaning up... Command /home/deploy/virtenv/bin/python -c "import setuptools, tokenize;file='/tmp/pip-XTwQiB-build/setup.py';exec(compile(getattr(tokenize, 'open', open)(file).read().replace('\r\n', '\n'), file, 'exec'))" install --record /tmp/pip-imyoFk-record/install-record.txt --single-version-externally-managed --compile --install-headers /home/deploy/virtenv/include/site/python2.7 failed with error code 1 in /tmp/pip-XTwQiB-build Storing debug log for failure in /home/deploy/.pip/pip.log (virtenv)deploy@api2:~$

[thomas-mangin]

There is no need to run pip and setup a virtualenv as exaproxy has no dependencies but we will look into it.

[thomas-mangin]

I noticed that this was fixed but not announced - however scripts installed in the etc directory are not chmod'ed +x .. I could not find a way to do it. Help welcomed.

[thomas-mangin]

chmod'ing the file was way more painful that it should have been. But the issue is now closed, it JUST took 5 months ... Sorry for that !