[07:41] <glyn> Hello. I just tried to install the charm tools on Mac OS X (Mavericks) via homebrew as per https://juju.ubuntu.com/docs/tools-charm-tools.html. I am using the latest version of homebrew and it is up to date. brew install juju gives me juju version 1.16.2-unknown-amd64, but this doesn't provide the charm subcommand., i.e. juju charm does not work (it gives "ERROR unrecognized command: juju charm"). I tried brew install charm-tools but this
[07:42] <glyn> juju charm now gives "Traceback (most recent call last):   File "/usr/local/bin/juju-charm", line 5, in <module>     from pkg_resources import load_entry_point ImportError: No module named pkg_resources ERROR exit status 1"
[07:43] <glyn> I just wanted to (a) point this out so the docs can be corrected and (b) see if anyone here knew how to fix the problem (assuming the docs are simply out of date).
[07:54] <glyn> I guess it's a bad time, especially in the US. I'll come back later to see if anyone was around.
[08:23] <glyn> Giving up. Some other time...
[18:38] <hazmat> jcastro, marcoceppi a github mp.. https://github.com/charms/joomla/pull/1
[18:39] <marcoceppi> hazmat: omg!
[18:39] <marcoceppi> IT'S HAPPENING
[18:40]  * marcoceppi reviews
[18:44] <hazmat> marcoceppi, :-) cool. i'm going to have some meetings next week on some foundational work items on the road to proper gh support.
[18:55] <hazmat> marcoceppi, did you see glynn's error report for charm tools on osx?
[18:55] <hazmat> er. glyn
[18:55] <marcoceppi> hazmat: yeah, it's too bad he's not on I would have told hiim to use pip for the time being
[18:55] <marcoceppi> hazmat: it's a known issue that we broke brew
[18:55] <marcoceppi> and that we're broken in brew
[18:55] <hazmat> marcoceppi, we ?
[18:55] <marcoceppi> hazmat: the royal we, charm-tools
[18:56] <marcoceppi> aka me
[18:56] <marcoceppi> :(
[18:56] <hazmat> marcoceppi, if it works in virtualenv / pip.. i'd suggest we == homebrew
[18:56] <hazmat> well that the issue lies there
[18:56] <hazmat> or the brew def thingy
[18:56] <marcoceppi> hazmat: it does, the formula isn't properly setup to work in brew
[18:57] <hazmat> gotcha
[18:57] <marcoceppi> hazmat: https://github.com/mxcl/homebrew/issues/23378#issuecomment-26665565
[19:20] <Azendale> what is the normal way of dealing with charm helpers and revision control? Should I ignore the charm helpers folder? Include it?
[19:23] <marcoceppi> Azendale: include it, it's ignored during reviews. Soon charm-helpers will be available via a debian package and you won't need to embed anymore
[19:24] <Azendale> marcoceppi: Ok, thanks
[19:26] <Azendale> marcoceppi: Trying my hand at creating an ejabberd charm, we'll see how far I get. The config file is in yaml though, so that part should be easy
[19:27] <marcoceppi> Azendale: awesome! let me know if you have any questions
[19:34] <Azendale> marcoceppi: Is it safe to assume python3 on this? Or do I need to either install python3 or just use python 2.x?
[19:35] <marcoceppi> Azendale: it depends on the series the charm is targeted to. If you target the charm at the trusty series, then python3 will be installed by default, with precise, you'll need to install it
[19:35] <marcoceppi> Azendale: it's safe to just not make any assumptions
[19:36] <Azendale> marcoceppi: what about saucy?
[19:36] <marcoceppi> Azendale: we don't recommend you target charms at non-LTS series
[19:37] <marcoceppi> Azendale: However, I'm not 100% sure of the saucy python status, to be safe just be explicit in your install hook for dpendencies
[19:41] <Azendale> marcoceppi: So, the hooks get everything from environment variables, not anything passed to them, right? I'm just thinking if I do a script that installs python3 and then calls a python3 file, do I need to pass anything on?
[19:41] <marcoceppi> Azendale: it's all environment variables, you should be fine to do that (lots of charms do)