[15:08] <ennoble> does anyone use jujuclient.py?
[15:16] <lazyPower> ennoble: deployer and a few other tools are based on it
[15:23] <ennoble> lazyPower: Is it still actively being maintained? It seems like there haven't been many changes to juju client in about six months.
[15:48] <lazyPower> ennoble: i cant say for certain that we are maintaining it, but as its a core utility of deployer, i'd default to saying it is under maintenance - but isn't actively receiving code changes as its stabilized for our needs today.
[15:58] <ennoble> lazyPower: thx, the Actions code in it has gotten more broken as juju-core has iterated under it. I'm guess I'm one of the few people using that
[16:12] <lazyPower> ennoble: ah, have you filed a bug against the broken behavior?
[16:50] <marcoceppi> ennoble: it's still maintained
[17:43] <beisner> hi coreycb + gnuoy` - fyi, the os next charms will need a c-h sync to pull in the liberty uca charmhelpers/fetch bit from r425   once that is done, we can begin to exercise the charms and packages.
[18:05] <coreycb> beisner, ok good so that's all ready for a sync?
[18:06] <beisner> coreycb, afaik, that should do it.  i locally syncd in a couple at random, which got me past "Unsupported cloud: source option trusty-liberty/proposed" and onto bigger/better issues ;-)
[18:08] <beisner> coreycb, fyi, jp has landed the liberty pkg versions helper bits, and i had already landed liberty amulet origin/source bits.
[18:14] <coreycb> beisner, great, I can work on the sync
[18:22] <beisner> coreycb, awesome, thanks!
[18:23] <coreycb> beisner, np!
[19:16] <beisner> wolsen, coreycb - while extending/refactoring the rmq amulet tests, i'm running into some issues along the release edges (precise & vivid).  middle ground combos ok.   i'm going to start raising those as bugs, and only enabling amulet tests in my MP for known-passing combos, so I can finally get that refactor bit landed.
[19:16] <beisner> wolsen, coreycb - first one is bug 1485722 ... will finish getting details on the precise issues and file separately.
[19:16] <mup> Bug #1485722: rmq on >= vivid has mnesia (no data dir) <amulet> <openstack> <uosci> <rabbitmq-server (Juju Charms Collection):New> <https://launchpad.net/bugs/1485722>
[19:32] <ennoble> lazyPower, marcoceppi: Yes, I submitted a bug for 1.23 https://bugs.launchpad.net/python-jujuclient/+bug/1455302 but the Actions() is completely broken for juju 1.24
[19:32] <mup> Bug #1455302: enqueue_units doesn't correctly pass parameters to action <python-jujuclient:New> <https://launchpad.net/bugs/1455302>
[19:32] <marcoceppi> ennoble: odd, I was able to use it
[19:49] <ennoble> marcoceppi: the issue looks like if you have a '-' in the unit name it fails
[19:57] <ennoble> marcoeppi: and the issue that I mentioned in my bug report prevents parameters from being specified (there is a fix in the bug report though)
[20:34] <skylerberg> The following appears in the charm testing documentation: "a sub-directory named 'tests' will be scanned by a test runner for executable files matching the glob *.test"
[20:35] <skylerberg> Is this true? or are all executables run?
[20:42] <lazyPower> skylerberg: anything with chmod +x is executed
[20:42] <lazyPower> there is no requirement of the file being [a-zA-z0-9].test
[20:42] <skylerberg> Okay, I will file a bug against the documentation then. Thanks.
[20:42] <lazyPower> thanks for finding that and pointing it out skylerberg
[23:41] <beisner> coreycb, just hit this for the first time in an ol' stale bundle.  woot for good feedback!    ...blocked    Charm has reached end-of-life. Please use neutron-gateway charm.