[10:52]  * popey wonders if anyone is planning on looking at bug 1159020
[10:52] <_mup_> Bug #1159020: SyntaxError: invalid syntax <juju:Confirmed> < https://launchpad.net/bugs/1159020 >
[10:54] <mgz> popey: you need to poke someone capable of fixing it
[10:54] <popey> name names! :D
[10:54] <mgz> it's good to keep bugging, but... this seems python distro/lxc related, rather than juju per se
[10:54] <popey> ah, good point
[10:55] <mgz> so, serge or barry would be my starters
[10:55] <popey> thanks
[10:55] <mgz> I also want to know what's going on with it so I can announce the 0.7 release and get it in raring
[10:57] <mgz> ...hm, may be worth a mailing list post
[11:15] <mgz> popey: have sent an email asking for help
[11:16] <popey> oh thanks!
[11:41] <popey> so in the meantime I have used juju on my home server running precise..
[11:41] <popey> I did the bootstrap, juju deploy etherpad-lite, then juju expose etherpad-lite
[11:41] <popey> which all seemed to work well \/
[11:41] <popey> er, \o/
[11:41] <popey> however it's given the instance a private address on the server, how can I easily make that accessible to other machines on my network?
[11:42] <popey> http://paste.ubuntu.com/5689155/  is what it looks like at the moment
[11:44] <popey> hmm, guessing that's some kind of lxc bridged connection?
[11:45] <popey> http://s3hh.wordpress.com/2011/05/17/lxc-with-bridged-network/ looks handy \o/
[12:36] <marcoceppi_> popey: I would hope that works, but I'm not confident as I think Juju sets up it's own bridge interface during bootstrap
[12:43]  * popey tries it out with a fiddle to the lxc.conf
[13:00] <marcoceppi> I know I asked a little while ago, but at this point we're pretty serious about breaking charms during upgrade-charm event cycle. (just to confirm)
[13:42] <jcastro> popey: if you figure that out, please document it!
[13:42] <popey> k
[14:11] <jcastro> m_3: heya how did the jenkins thing go?
[14:11] <jcastro> you hook up with IS?
[14:23] <m_3> jcastro: nope, I'm just gonna hook up with jamespage to debug it
[14:23] <jcastro> marcoceppi: oh hey, you're on queue duty this week (see topic)
[14:23] <marcoceppi> yup, looking at the queue now
[14:26] <mgz> popey: are you up for some raring experimentation for your lxc issue?
[14:27] <popey> sure mgz
[14:45] <mgz> popey: okay, can you try using the branch lp:~gz/juju/lxc_env_testing locally?
[14:47] <mgz> should be able to just branch and do `python setup.py install --user` then run from your ~/.local/bin
[14:52] <hazmat> mgz, no need to warn, path manipulation is part of local to allow for dev envs
[14:53] <mgz> I just want to see if it appears in the log, I don't think this is the right fix
[14:53] <mgz> (if it's this, the lxc scripts are what need changing)
[14:57] <popey> ok, so I have installed..
[14:57] <popey> just cd ~/.local/bin && juju status  ?
[14:57] <popey> probably need to bootstrap on this actually, not run properly yet
[14:58] <popey> ok, thats better, bootstrap is working, status returns something sane
[14:58] <popey> and its now deploying etherpad-lite
[15:01] <popey> mgz: http://paste.ubuntu.com/5689628/
[15:03] <mgz> heh, I can't code
[15:05] <mgz> need to work out what the lxc tests require apart from TEST_SUDO to run
[15:05] <mgz> either way, shows that you did have some PYTHON envvar breaking things
[15:06] <mgz> popey: pull, setup.py install --user again and re-run that command
[15:06] <mgz> then paste the same log please
[15:07] <popey> k
[15:08] <popey> mgz: http://paste.ubuntu.com/56899657
[15:08] <popey> er
[15:09] <popey> http://paste.ubuntu.com/5689657
[15:09] <popey> hang on, my mess, let me start again
[15:10] <popey> http://paste.ubuntu.com/5689662 mgz
[15:11] <mgz> okay, so that's resolvable
[15:34] <popey> super