| 2016-05-12 00:33:33 |
Kyle Fazzari |
bug |
|
|
added bug |
| 2016-05-12 00:52:32 |
Kyle Fazzari |
summary |
Add support for confinement flag |
Add support for confinement property |
|
| 2016-05-12 01:11:51 |
Kyle Fazzari |
snapcraft: status |
New |
In Progress |
|
| 2016-05-12 01:11:55 |
Kyle Fazzari |
snapcraft: importance |
Undecided |
High |
|
| 2016-05-12 01:11:57 |
Kyle Fazzari |
snapcraft: assignee |
|
Kyle Fazzari (kyrofa) |
|
| 2016-05-12 01:12:00 |
Kyle Fazzari |
snapcraft: milestone |
|
2.9 |
|
| 2016-05-12 15:36:09 |
Kyle Fazzari |
description |
[Impact]
* Snaps need to be able to specify if they require devmode or if they can be run confined. This will allow for snapd to provide reasonable errors if one tries to install a snap that cannot run successfully under confinement.
* The YAML property should be called "confinement," and it should have two options: "devmode" and "enabled." It should be required, and `snapcraft init` should set it to "devmode."
[Test Case]
* Run `snapcraft init`. Make sure "confinement" is "devmode."
* Create a valid snapcraft.yaml and run `snapcraft` on it. Make sure the "confinement" value gets copied to the `snap.yaml`.
* Create a valid snapcraft.yaml and remove the "confinement" property. Run `snapcraft`. It should return an error since "confinement" is required.
[Regression Potential]
* snapcraft.yaml validation could be incorrect (required properties may not be required correctly, etc.) |
[Impact]
* Snaps need to be able to specify if they require devmode or if they can be run confined. This will allow for snapd to provide reasonable errors if one tries to install a snap that cannot run successfully under confinement.
* The YAML property should be called "confinement," and it should have two options: "devmode" and "strict." It should be required, and `snapcraft init` should set it to "devmode."
[Test Case]
* Run `snapcraft init`. Make sure "confinement" is "devmode."
* Create a valid snapcraft.yaml and run `snapcraft` on it. Make sure the "confinement" value gets copied to the `snap.yaml`.
* Create a valid snapcraft.yaml and remove the "confinement" property. Run `snapcraft`. It should return an error since "confinement" is required.
[Regression Potential]
* snapcraft.yaml validation could be incorrect (required properties may not be required correctly, etc.) |
|
| 2016-05-12 16:03:31 |
Kyle Fazzari |
description |
[Impact]
* Snaps need to be able to specify if they require devmode or if they can be run confined. This will allow for snapd to provide reasonable errors if one tries to install a snap that cannot run successfully under confinement.
* The YAML property should be called "confinement," and it should have two options: "devmode" and "strict." It should be required, and `snapcraft init` should set it to "devmode."
[Test Case]
* Run `snapcraft init`. Make sure "confinement" is "devmode."
* Create a valid snapcraft.yaml and run `snapcraft` on it. Make sure the "confinement" value gets copied to the `snap.yaml`.
* Create a valid snapcraft.yaml and remove the "confinement" property. Run `snapcraft`. It should return an error since "confinement" is required.
[Regression Potential]
* snapcraft.yaml validation could be incorrect (required properties may not be required correctly, etc.) |
[Impact]
* Snaps need to be able to specify if they require devmode or if they can be run confined. This will allow for snapd to provide reasonable errors if one tries to install a snap that cannot run successfully under confinement.
* The YAML property should be called "confinement," and it should have two options: "devmode" and "strict." It should be required, and `snapcraft init` should set it to "devmode."
* The "confinement" YAML property should be copied into the resulting `snap.yaml`.
[Test Case]
* Run `snapcraft init`. Make sure "confinement" is "devmode."
* Create a valid snapcraft.yaml and run `snapcraft` on it. Make sure the "confinement" value gets copied to the `snap.yaml`.
* Create a valid snapcraft.yaml and remove the "confinement" property. Run `snapcraft`. It should return an error since "confinement" is required.
[Regression Potential]
* snapcraft.yaml validation could be incorrect (required properties may not be required correctly, etc.) |
|
| 2016-05-12 16:07:13 |
Kyle Fazzari |
snapcraft: importance |
High |
Wishlist |
|
| 2016-05-19 14:44:13 |
Kyle Fazzari |
description |
[Impact]
* Snaps need to be able to specify if they require devmode or if they can be run confined. This will allow for snapd to provide reasonable errors if one tries to install a snap that cannot run successfully under confinement.
* The YAML property should be called "confinement," and it should have two options: "devmode" and "strict." It should be required, and `snapcraft init` should set it to "devmode."
* The "confinement" YAML property should be copied into the resulting `snap.yaml`.
[Test Case]
* Run `snapcraft init`. Make sure "confinement" is "devmode."
* Create a valid snapcraft.yaml and run `snapcraft` on it. Make sure the "confinement" value gets copied to the `snap.yaml`.
* Create a valid snapcraft.yaml and remove the "confinement" property. Run `snapcraft`. It should return an error since "confinement" is required.
[Regression Potential]
* snapcraft.yaml validation could be incorrect (required properties may not be required correctly, etc.) |
[Impact]
* Snaps need to be able to specify if they require devmode or if they can be run confined. This will allow for snapd to provide reasonable errors if one tries to install a snap that cannot run successfully under confinement.
* The YAML property should be called "confinement," and it should have two options: "devmode" and "strict." It should be optional, and `snapcraft init` should set it to "devmode."
* The "confinement" YAML property should be copied into the resulting `snap.yaml`.
[Test Case]
* Run `snapcraft init`. Make sure "confinement" is "devmode."
* Create a valid snapcraft.yaml and run `snapcraft` on it. Make sure the "confinement" value gets copied to the `snap.yaml`.
* Create a valid snapcraft.yaml and remove the "confinement" property. Run `snapcraft`. It should print a hint about defaulting to "strict", and "confinement: strict" should be in the resulting `snap.yaml`.
[Regression Potential]
* snapcraft.yaml validation could be incorrect (required properties may not be required correctly, etc.) |
|
| 2016-05-19 15:03:43 |
Kyle Fazzari |
description |
[Impact]
* Snaps need to be able to specify if they require devmode or if they can be run confined. This will allow for snapd to provide reasonable errors if one tries to install a snap that cannot run successfully under confinement.
* The YAML property should be called "confinement," and it should have two options: "devmode" and "strict." It should be optional, and `snapcraft init` should set it to "devmode."
* The "confinement" YAML property should be copied into the resulting `snap.yaml`.
[Test Case]
* Run `snapcraft init`. Make sure "confinement" is "devmode."
* Create a valid snapcraft.yaml and run `snapcraft` on it. Make sure the "confinement" value gets copied to the `snap.yaml`.
* Create a valid snapcraft.yaml and remove the "confinement" property. Run `snapcraft`. It should print a hint about defaulting to "strict", and "confinement: strict" should be in the resulting `snap.yaml`.
[Regression Potential]
* snapcraft.yaml validation could be incorrect (required properties may not be required correctly, etc.) |
[Impact]
* Snaps need to be able to specify if they require devmode or if they can be run confined. This will allow for snapd to provide reasonable errors if one tries to install a snap that cannot run successfully under confinement.
* The YAML property should be called "confinement," and it should have two options: "devmode" and "strict." It should be optional, and `snapcraft init` should set it to "devmode."
* The "confinement" YAML property should be copied into the resulting `snap.yaml`.
* Example YAML:
name: foo
version: 1
summary: foo
description: foo
confinement: devmode
parts:
foo:
plugin: nil
[Test Case]
* Run `snapcraft init`. Make sure "confinement" is "devmode."
* Create a valid snapcraft.yaml and run `snapcraft` on it. Make sure the "confinement" value gets copied to the `snap.yaml`.
* Create a valid snapcraft.yaml and remove the "confinement" property. Run `snapcraft`. It should print a hint about defaulting to "strict", and "confinement: strict" should be in the resulting `snap.yaml`.
[Regression Potential]
* snapcraft.yaml validation could be incorrect (required properties may not be required correctly, etc.) |
|
| 2016-05-23 17:40:27 |
Kyle Fazzari |
bug task added |
|
click-reviewers-tools |
|
| 2016-05-23 19:27:03 |
Jamie Strandboge |
click-reviewers-tools: status |
New |
Fix Released |
|
| 2016-05-24 14:17:47 |
Sergio Schvezov |
snapcraft: status |
In Progress |
Fix Committed |
|
| 2016-05-24 14:28:08 |
Sergio Schvezov |
bug task added |
|
snapcraft (Ubuntu) |
|
| 2016-05-24 14:28:22 |
Sergio Schvezov |
nominated for series |
|
Ubuntu Yakkety |
|
| 2016-05-24 14:28:22 |
Sergio Schvezov |
bug task added |
|
snapcraft (Ubuntu Yakkety) |
|
| 2016-05-24 14:28:22 |
Sergio Schvezov |
nominated for series |
|
Ubuntu Xenial |
|
| 2016-05-24 14:28:22 |
Sergio Schvezov |
bug task added |
|
snapcraft (Ubuntu Xenial) |
|
| 2016-05-24 14:28:32 |
Sergio Schvezov |
snapcraft (Ubuntu Xenial): milestone |
|
xenial-updates |
|
| 2016-05-24 20:47:48 |
Martin Pitt |
bug |
|
|
added subscriber Ubuntu Stable Release Updates Team |
| 2016-05-24 20:47:49 |
Martin Pitt |
bug |
|
|
added subscriber SRU Verification |
| 2016-05-24 20:47:52 |
Martin Pitt |
tags |
|
verification-needed |
|
| 2016-05-25 07:51:17 |
Launchpad Janitor |
snapcraft (Ubuntu Yakkety): status |
New |
Fix Released |
|
| 2016-05-25 13:32:02 |
Chris J Arges |
snapcraft (Ubuntu Xenial): status |
New |
Fix Committed |
|
| 2016-05-25 18:39:43 |
Jamie Strandboge |
bug task added |
|
click-reviewers-tools (Ubuntu) |
|
| 2016-05-25 18:39:54 |
Jamie Strandboge |
click-reviewers-tools (Ubuntu Yakkety): status |
New |
Fix Released |
|
| 2016-05-25 18:39:58 |
Jamie Strandboge |
click-reviewers-tools (Ubuntu Xenial): status |
New |
Fix Committed |
|
| 2016-05-25 18:40:01 |
Jamie Strandboge |
click-reviewers-tools (Ubuntu Xenial): assignee |
|
Jamie Strandboge (jdstrand) |
|
| 2016-05-25 18:40:03 |
Jamie Strandboge |
click-reviewers-tools (Ubuntu Yakkety): assignee |
|
Jamie Strandboge (jdstrand) |
|
| 2016-05-25 18:44:21 |
Jamie Strandboge |
tags |
verification-needed |
verification-done |
|
| 2016-05-27 17:40:27 |
Sergio Schvezov |
snapcraft: status |
Fix Committed |
Fix Released |
|
| 2016-05-30 19:42:19 |
Launchpad Janitor |
snapcraft (Ubuntu Xenial): status |
Fix Committed |
Fix Released |
|
| 2016-05-30 19:42:44 |
Adam Conrad |
removed subscriber Ubuntu Stable Release Updates Team |
|
|
|
| 2016-05-30 19:43:30 |
Launchpad Janitor |
click-reviewers-tools (Ubuntu Xenial): status |
Fix Committed |
Fix Released |
|
