I'm not sure what the specific bug is, but if I'm running a development version of Juju, I end up with:
$ juju charm create
usage: /usr/bin/juju-charm subcommand
Available subcommands are:
admin
create
get
getall
list
promulgate
proof
review
review-queue
search
subscribers
unpromulgate
update
ERROR subprocess encountered error code 1
Note that I ran "juju charm create" and it tells me that it is one of the subcommands, but it doesn't actually work.
Now if I run:
/usr/bin/juju charm create
I get a nice help text:
usage: charm-create [-h] charmname [charmhome]
charm-create: error: too few arguments
Also, even if I use the right syntax, charm create doesn't actually work with Dev juju:
$ juju charm create foobar
usage: /usr/bin/juju-charm subcommand
Available subcommands are:
admin
create
...
Mabye something has changed in trunk about how parameters are getting passed to plugins?
I'm not sure what the specific bug is, but if I'm running a development version of Juju, I end up with:
$ juju charm create
usage: /usr/bin/juju-charm subcommand
Available subcommands are:
admin
create
get
getall
list
promulgate
proof
review
review-queue
search
subscribers
unpromulgate
update
ERROR subprocess encountered error code 1
Note that I ran "juju charm create" and it tells me that it is one of the subcommands, but it doesn't actually work.
Now if I run:
/usr/bin/juju charm create
I get a nice help text:
usage: charm-create [-h] charmname [charmhome]
charm-create: error: too few arguments
Also, even if I use the right syntax, charm create doesn't actually work with Dev juju:
$ juju charm create foobar
usage: /usr/bin/juju-charm subcommand
Available subcommands are:
admin
create
...
Mabye something has changed in trunk about how parameters are getting passed to plugins?