Poorly worded error when installing a local snap without assertions
Bug #1621575 reported by
Evan
This bug affects 4 people
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| snapd |
Confirmed
|
Undecided
|
Unassigned | ||
Bug Description
$ snap install cassandra_
error: cannot find signatures with metadata for snap "cassandra_
This error message does a poor job of describing what went wrong and what I can do to remedy the situation.
Might I suggest something like:
$ snap install cassandra_
Cannot install a local snap without an accompanying local snap-build assertion.
Please provide a snap-build assertion and try again.
Alternatively, re-run with --force-dangerous if you trust the snap content.
| summary: |
- No assertions when installing local snap error is poorly worded + Poorly worded error when trying to install a local snap without + assertions |
| summary: |
- Poorly worded error when trying to install a local snap without - assertions + Poorly worded error when installing a local snap without assertions |
| Changed in snappy: | |
| status: | New → Confirmed |
Revision history for this message
| Celso Providelo (cprov) wrote | #1 |
Revision history for this message
| Natalia Bidart (nataliabidart) wrote | #2 |
Revision history for this message
| XiaoGuo, Liu (liu-xiao-guo) wrote | #3 |
Revision history for this message
| XiaoGuo, Liu (liu-xiao-guo) wrote | #4 |
| tags: | added: eco-team |
| affects: | snappy → snapd |
To post a comment you must log in.
Evan,
snap-build doesn't fill the whole trust-path for a snap:
[snap-build =>] snap-revision => snap-declaration => account-key => account
and since it is either trusted (fully) or not, the clearest thing to do is to suggest `--force-
Other more elaborate plan would be to design a tool for creating and signing all the assertions needed to distribute snaps safely (and pack them please, 5+ files would be annoying).