Strange error when layered charm destination exists
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
charm-tools (Ubuntu) |
New
|
Undecided
|
Unassigned |
Bug Description
Use-case: You have a "normal" Charm and you start porting it to composer. You copy the charm from /trusty/mycharm to /layers/mycharm. You start splitting the charm in layers and run `charm generate mycharm`
Expected result: You get an error explaining that the Charm /trusty/mycharm already exists, and would be overwritten by `charm generate`
Result you get: The following error message:
composer: Added unexpected file, should be in a base layer: juju-client/
Traceback (most recent call last):
File "/tmp/charm-
load_
File "/tmp/charm-
composer()
File "/tmp/charm-
self.validate()
File "/tmp/charm-
"Unable to continue due to unexpected modifications (try --force)")
ValueError: Unable to continue due to unexpected modifications (try --force)
I think my use-case will happen a lot with people just starting with charms layers. It would be great if the error message could be a little more explanatory, and not give a python traceback...