[00:14] <daker> pleia2: try : make clean
[00:15] <daker> then retype the same commands as before
[00:16] <pleia2> I've doen that several times :)
[00:16] <pleia2> (retried with 1.3 too)
[00:18] <daker> pleia2: which version 12.04 ?
[00:18] <pleia2> yeah
[00:18] <daker> pleia2: then try :
[00:18] <daker> cd ./loco_directory/ && ../env/bin/python manage.py shell
[00:19] <daker> then paste this :
[00:19] <daker> from django.core.management import execute_manager
[00:20] <JoseeAntonioR> IdleOne: I can tell you what I did (I'm 15)
[00:21] <JoseeAntonioR> IdleOne: if you still need it, just ping me
[00:22] <IdleOne> JoseeAntonioR: the info is not for me but for vibhav
[00:24] <JoseeAntonioR> vibhav: what do you exactly need to know? you can attend with a legal guardian (parents count as such), and you can't obviously drink as per country legislations
[00:26] <pleia2> daker: ok, done (had to make init again, forgot I had make cleaned after trying 1.3)
[00:26] <pleia2> no errors
[00:27] <mhall119> nigelb: summit moved to 1.3, ltp is still 1.2 I think
[00:28] <mhall119> pleia2: the make file isn't very smart, so if you get an error during make init you usually have to delete the ./env/ directory and start ove
[00:29] <pleia2> clean removes env
[00:29] <pleia2> (it's the first thing it does :))
[00:29] <pleia2> clean: rm -rf env/
[00:29] <pleia2> etc
[00:30] <mhall119> ok
[00:31] <mhall119> pleia2: are you still getting the same error?
[00:31] <pleia2> yep
[00:31] <nigelb> mhall119: if ltp is on 1.2 the requirements file hasn't been updated.
[00:31] <mhall119> it's odd, because it found django just fine when it ran syncdb and migrate...
[00:31] <mhall119> nigelb: it could be 1.1
[00:32] <nigelb> that's the exact same thought I had too.
[00:32] <mhall119> whatever the Lucid version is
[00:32] <pleia2> requirements fiel has 1.1.2
[00:32] <nigelb> It ran syncdb and migrate just fine :/
[00:33] <nigelb> pleia2: if you haven't run make clean yet, can you try "cd ./loco_directory/ && ../env/bin/python manage.py help"?
[00:33] <pleia2> this is when it dies: cd ./loco_directory/ && ../env/bin/python manage.py init
[00:33] <mhall119> wait, mine runs cd ./loco_directory/ && ../env/bin/python manage.py init-ld
[00:33] <mhall119> pleia2: try running ^^
[00:34] <mhall119> init-ld instead of init
[00:34] <pleia2> Unknown command: 'init-ld'
[00:34] <pleia2> init is in the help though (init-ld isn't)
[00:34] <daker> no mhall119 it's init
[00:35] <mhall119> pleia2: what revision?
[00:35] <pleia2> revision of..?
[00:35] <mhall119> of loco directory, bzr revno
[00:36] <pleia2> oh I just pulled the default one from lp
[00:36] <pleia2> 545
[00:36] <nigelb> oh man
[00:36] <nigelb> I think I know why this is failing.
[00:36] <mhall119> oh, I still have 527
[00:36] <daker> mhall119: she can passe the init step since i gave her a fresh db
[00:36] <nigelb> subprocess.call(["python", "manage.py", "compilemessages"])
[00:36] <nigelb> that command isn't finding the right path.
[00:37] <nigelb> that's why it can't find django
[00:37] <nigelb> line 22 in init.py
[00:37] <mhall119> nigelb: that should work
[00:37] <nigelb> (how did this ever work?)
[00:37] <mhall119> since it'll be in the virtualenv, 'python' will resolve to the virtualenv's version
[00:38] <mhall119> oh wait....maybe not?
[00:38] <nigelb> it's not actively in a virtualenv
[00:38] <mhall119> since we're calling python, not switching to the virtualenv and then calling it
[00:38] <nigelb> Exactly.
[00:38] <mhall119> yes, you're right
[00:39] <nigelb> Hah, I'm glad my debugging skills are good even after an all-nighter :P
[00:39] <daker> pleia2: just run : make run
[00:40] <pleia2> daker: I'm not using your db because I'm trying to write docs for this to help others who were interested in hacking on ltp
[00:40] <pleia2> if we can fix this it would be better to do that instead of having to have you ship fresh dbs to people :)
[00:41] <mhall119> pleia2: I'll need to start over with a clean branch of trunk
[00:41] <mhall119> I'm afraid I have too much cruft in my old setup
[00:41]  * pleia2 nods
[00:41] <JoseeAntonioR> are we having a dentist at uds-r? :P
[00:44] <nigelb> mhall119: I still maintain that it's easier to give everyone individual commands to run instead of trying to automate it.
[00:44] <nigelb> It's harder for us to debug if something goes wrong in the automatic one-step way.
[00:46] <mhall119> nigelb: I'll buy a beer for you in Copenhagen if you do that
[00:46] <pleia2> so, how to manually tell init.py where to look?
[00:46] <mhall119> pleia2: run: source ./env/bin/activate
[00:46] <mhall119> that'll put your shell into the virtualenv
[00:46] <mhall119> then you should be able to run just "python manage.py init"
[00:47] <mhall119> (run just 'deactivate' to leave the virtualenv)
[00:47] <pleia2> ah, much better :)
[00:48] <nigelb> mhall119: Oh, I wrote it for summit. It shouldn't be too hard. I'll write it and put it in readthedocs :D
[00:49] <pleia2> and running \o/
[00:49] <nigelb> mhall119: I won't be in copenhagen, so buy a beer for pleia2 if she makes it ;-)
[00:52] <daker> mhall119, nigelb to fix it : subprocess.call([sys.executable, "manage.py", "compilemessages"])
[00:55] <daker> nigelb: mhall119 or maybe we can just use fabric ?
[00:57] <pleia2> daker: that did it \o/
[00:57] <pleia2> now it completes make init w/o error
[00:57] <daker> woow
[01:00] <pleia2> alright, just getting this running is enough for today, I shall bug you guys about what I do next another day :)
[01:01] <daker> pleia2: FYI, you'll need to provide the db in the doc because anyone who want to work on LTP will need data (teams,events, users, etc...) the db has everything in it otherwise they will need to run python manage.py import-live-data and you will have to wait about 1 hour to fetch the data from l.u.c, right mhall119 ?
[01:02] <pleia2> oh fun
[01:02] <daker> :)
[01:06] <pleia2> ah, much more useful with data in it :)
[01:39] <daker> mhall119: review it https://code.launchpad.net/~daker/loco-team-portal/fix-python-path/+merge/120276 :)
[17:08] <daker> nigelb: any idea why this hasn't been merged https://code.launchpad.net/~daker/loco-team-portal/fix-python-path/+merge/120276 ?
[17:10] <nigelb> daker: sec, looking
[17:10] <cjohnston> cause tarmac still isnt working :-P
[17:10]  * cjohnston rruns
[17:15] <nigelb> cjohnston: well, if it isn't working, it's your fault. you never told me after that.
[17:19] <cjohnston> I haven't had a chance to use it because I'm still waiting on you to review some code
[17:20] <nigelb> by "you", you mean mh	, right?
[17:20] <nigelb> by "you", you mean mhall119, right?
[17:20] <cjohnston> no. the same review I asked you to do
[17:21] <cjohnston> he has others to do
[17:21] <cjohnston> and noone does any of them