image-status strict confinement snap #6
Closed
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
added 4 commits
February 16, 2018 11:08
… when querying the ubuntu-cloudimage-keyring
|
I pulled this just dropping the rename commit. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
I have been using
image-statusmore and more and to make it easier to install I have created snap/snapcraft.yaml which builds a strict confinement snap for image-status.You can test this by installing the temporarily named "image-status-philroche"
sudo snap install image-status-philrocheand test using
/snap/bin/image-status-philroche.image-status cloud-daily xenialFeel free to change snap name and register repo with https://build.snapcraft.io/ or I can do this if you like.