confusing error when the binary is not found and it has the same name of the app
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Snapcraft |
Fix Released
|
Low
|
Leo Arias | ||
snapcraft (Ubuntu) |
Fix Released
|
Undecided
|
Unassigned | ||
Xenial |
Fix Released
|
Undecided
|
Unassigned | ||
Yakkety |
Fix Released
|
Undecided
|
Unassigned |
Bug Description
I've made a mistake when trying to snap a CLI app. In the command section I entered the name of a bin that doesn't exist. I got this error back:
The specified command 'hollywood' defined in 'hollywood' does not exist or is not executable
The error is ok, but we could improve it with something like:
The specified command 'hollywood' defined in *the 'hollywood' app* does not exist or is not executable.
Here's the relevant part of my snapcraft.yaml:
apps:
hollywood:
command: hollywood
[Impact]
* New users are likely to make this error, and the error might confuse them more.
[Test Case]
* Define a snapcraft.yaml with a wrong command path
* Run snapcraft
[Regression Potential]
* Extremely low. The fix is to change a string, that won't affect the error handling of existing code paths.
Changed in snapcraft: | |
assignee: | nobody → Leo Arias (elopio) |
milestone: | none → 2.10 |
Changed in snapcraft: | |
status: | In Progress → Fix Committed |
Changed in snapcraft (Ubuntu Xenial): | |
milestone: | none → xenial-updates |
Changed in snapcraft: | |
status: | Fix Committed → Fix Released |
https:/ /github. com/ubuntu- core/snapcraft/ pull/541