snap-confine should respond to --version
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
snap-confine |
Fix Released
|
Wishlist
|
Zygmunt Krynicki | ||
snap-confine (Ubuntu) |
New
|
Undecided
|
Unassigned | ||
Xenial |
Fix Committed
|
Undecided
|
Unassigned | ||
Yakkety |
Fix Committed
|
Undecided
|
Unassigned |
Bug Description
[Impact]
snap-confine didn't know its own version number which was always a problem in core images where people would not really know which version was used to build the core snap. With this "snap-confine --version" now does the right thing.
[Test Case]
The test case can be found here:
https:/
The test case is ran automatically for each pull request and for each final release. It can be reproduced manually by executing the shell commands listed in the prepare/
The commands there assume that snapd and snap-confine are installed.
No other additional setup is necessary.
[Regression Potential]
* Regression potential is almost non-existent as all of the existing tests work correctly (so snap-confine behaves as before).
[Other Info]
* snap-confine is technically an integral part of snapd which has an SRU exception and is allowed to introduce new features and take advantage of accelerated procedure. For more information see https:/
== # Pre-SRU bug description follows # ==
In core images it is sometimes hard to know which version of snap-confine is being used. We should respect the --version command-line option.
Changed in snap-confine: | |
status: | In Progress → Fix Released |
description: | updated |
tags: | added: verification-needed |
Hello Zygmunt, or anyone else affected,
Accepted snap-confine into yakkety-proposed. The package will build now and be available at https:/ /launchpad. net/ubuntu/ +source/ snap-confine/ 1.0.44- 0ubuntu1~ 16.10 in a few hours, and then in the -proposed repository.
Please help us by testing this new package. See https:/ /wiki.ubuntu. com/Testing/ EnableProposed for documentation how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users.
If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, and change the tag from verification-needed to verification-done. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification- failed. In either case, details of your testing will help us make a better decision.
Further information regarding the verification process can be found at https:/ /wiki.ubuntu. com/QATeam/ PerformingSRUVe rification . Thank you in advance!