Command snappy-remote should support --allow-unauthenticated from snappy install
Bug #1443676 reported by
Caio Begotti
This bug affects 4 people
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Snappy |
Invalid
|
Wishlist
|
Unassigned | ||
Ubuntu Developer Portal |
Invalid
|
Medium
|
Unassigned |
Bug Description
Right now when you are developing a .snap and Snappy fails with "signature verification failed with exit status 10" you end up without a way to install and test your package.
Ideally snappy-remote should support passing options to the install command it runs, at least --allow-
Changed in snappy-ubuntu: | |
status: | New → Confirmed |
importance: | Undecided → Wishlist |
affects: | snappy-ubuntu → snappy |
Changed in developer-ubuntu-com: | |
status: | New → Triaged |
importance: | Undecided → Medium |
Changed in developer-ubuntu-com: | |
status: | Triaged → Incomplete |
To post a comment you must log in.
Btw, I get that it does not happen in developer mode but otherwise snappy-remote would not be really useful in non-devel cases then?