| 2016-11-03 08:02:22 |
Zygmunt Krynicki |
description |
The environment variable SNAP_CONFINE_DEBUG should respond to values like "yes" "no" "1" and "0" instead to just being defined (even if empty). |
[Impact]
snap-confine respects SNAP_CONFINE_DEBUG environment variable. The presence of this variable, regardless of what the value is, enables diagnostic output. To have more predictable and sane behaviour only specific values will trigger diagnostic output. The values are "yes", "no", "0" and "1".
[Test Case]
The test case can be found here:
https://github.com/snapcore/snap-confine/blob/master/spread-tests/main/debug-flags/task.yaml
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/execute/restore phases manually.
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 the debug mode is not enabled by default and it was even easier to enable previously.
[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://wiki.ubuntu.com/SnapdUpdates
== # Pre-SRU bug description follows # ==
The environment variable SNAP_CONFINE_DEBUG should respond to values like "yes" "no" "1" and "0" instead to just being defined (even if empty). |
|
