>>>>> Andy Doan <[email protected]> writes:
> On 12/16/2013 12:48 PM, Para Siva wrote:
>> Hey Andy,
>>
>> Just in case I left that unclear/failed to understand in the standup
>> this morning..
>>
>> My confusion and import errors were caused by running
>> "./ci-utils/setup.py develop" as a standard user and running
>> "./ppa-assigner/setup.py create_db" as sudo. This caused import errors
>> of ci_utils when in the latter in django env's. The unit tests also
>> reported import errors. When both being run as a single user the error
>> is not occurring.
> good question. I suspect the problem you have is that when you became
root,
> you didn't source your venv. ie - this is what you probably need to do:
> bzr branch lp:ubuntu-ci-services-itself
> cd ubuntu-ci-services-itself/
> virtualenv venv
> . venv/bin/activate
> ./ci-utils/setup.py develop
> ./ppa-assigner/setup.py develop
> sudo -s # this is needed
> . venv/bin/activate # and also this
> ./ppa-assigner/setup.py create_db
/me blinks
7 commands to issue manually ? No tests ?
Are there ways to have automated tests for that so we *know* setting up
the env is automated ?
And people wonder why I dislike pip and its fallouts ? (This is just the
tip of the iceberg we're hitting here, pip won't work in prodstack as
is).
Vincent
--
Mailing list: https://launchpad.net/~canonical-ci-engineering
Post to : [email protected]
Unsubscribe : https://launchpad.net/~canonical-ci-engineering
More help : https://help.launchpad.net/ListHelp
