[15:39] <meebey> how can I start juju with full debug logging? juju -vvv seems to be deprecated and doesnt show all log calls either
[15:41] <meebey> found it: --show-log --debug
[15:41] <meebey> "verbose is deprecated with the current meaning, use show-log" that was a bit confusing, I thought show-log is a subcommand of juju instead of parameter
[19:04] <hazmat> meebey, https://lists.ubuntu.com/archives/juju/2013-September/002998.html
[19:04] <hazmat> meebey, debug-log is a the subcommand
[19:04] <hazmat> meebey, the link has the config to enable verbose agent logging
[19:05] <hazmat> meebey, for cli.. --debug does detailed looging, else -v for verbose
[19:05] <meebey> thanks
[19:34] <thumper> hazmat: please stop using -v for verbose
[19:34] <thumper> hazmat: the meaning of verbose is changing
[19:34] <thumper> hazmat: verbose will (RSN) mean 'show more output' and not be related to logging
[19:35] <thumper> user output and developer logging are two different things
[19:42] <hazmat> thumper, -v for what then?
[19:43] <hazmat> thumper, yes dev log and user log distinction understood, how is that not embodied by --debug vs -v ?
[19:43] <hazmat> and if its not.. then that's a ux bug imo
[19:45] <thumper> hazmat: --debug says "show me the debug log and set logging to DEBUG"
[19:45] <thumper> hazmat: -v should mean "show me more user output"
[19:45] <thumper> -q should be "show me no user output"
[19:45] <thumper> should, but isn't yet
[19:45] <thumper> it has been one of those annoying things I keep meaning to get around to fixing properly
[19:46] <hazmat> thumper, and that's exactly what i meant to convey
[19:46] <hazmat> re -v vs. --debug
[19:46] <thumper> hazmat: perhaps we should just file it as a bug :-)
[19:46] <thumper> at least it would then be tracked
[19:46] <thumper> hazmat: also, Hai!
[19:46] <hazmat> thumper, chairs on the deck imo.
[19:47]  * thumper looks confused
[19:50] <hazmat> thedac, also, Mauri ora! Kia ora!  :-)
[19:50] <hazmat> argh.. thumper ^
[19:51] <thumper> :)
[21:08] <rick_h_> is there any hack/way to trick juju into letting me deploy a local charm without creating the directory structure for series? I git clone the charm and just want to deploy it, but it really wants that series directory.
[22:24] <lazypower> rick_h_, i've tried that myself and have been unsuccessful
[22:24] <lazypower> rick_h_, the workflow i've adopted is to to keep a "in dev" and a "production" series of directories to islate what i'm checking vs what i'm deploying - and alias those
[22:27] <rick_h_> lazypower: cool, guess as long as I'm not the only one that thinks it should work a bit differently
[22:28] <lazypower> I've heard talks of the series going in metadata.yaml instead of being a forced portion of the dir structure
[22:28] <lazypower> but its not there yet
[22:28] <rick_h_> yea, that'll be a bit to settle out
[22:48] <marcoceppi> rick_h_: symlinks
[22:48] <marcoceppi> otherwise, no
[22:50] <rick_h_> marcoceppi: yea, but it rejects symlinks because you're trying to reach something outside the dir
[22:50] <rick_h_> marcoceppi: is there a symlink pattern that does work?