Activity log for bug #1350427

Date Who What changed Old value New value Message
2014-07-30 16:05:12 Pete Woods bug added bug
2014-07-30 16:05:37 Pete Woods description Following the apparmor policy updates a little while ago, scopes are now named after the hook short ID. For a scope package "package-name" with a hook "hook-name" to the directory "dir-name". { ... "hooks": { "HOOKNAME": { "scope": "DIRNAME", "apparmor": "apparmor.json" } }, "name": "PACKAGENAME" ... } The tool should look in "DIRNAME/PACKAGENAME_HOOKNAME.ini" for the the ini file. Following the apparmor policy updates a little while ago, scopes are now named after the hook short ID. For a scope package "package-name" with a hook "hook-name" to the directory "dir-name". manifest.json: {     ...     "hooks": {         "HOOKNAME": {             "scope": "DIRNAME",             "apparmor": "apparmor.json"         }     },    "name": "PACKAGENAME"     ... } The tool should look in "DIRNAME/PACKAGENAME_HOOKNAME.ini" for the the ini file.
2014-07-30 16:06:53 Pete Woods description Following the apparmor policy updates a little while ago, scopes are now named after the hook short ID. For a scope package "package-name" with a hook "hook-name" to the directory "dir-name". manifest.json: {     ...     "hooks": {         "HOOKNAME": {             "scope": "DIRNAME",             "apparmor": "apparmor.json"         }     },    "name": "PACKAGENAME"     ... } The tool should look in "DIRNAME/PACKAGENAME_HOOKNAME.ini" for the the ini file. Following the apparmor policy updates a little while ago, scopes are now named after the hook short ID. For a scope package "package-name" with a hook "hook-name" to the directory "dir-name". manifest.json: {     ...     "hooks": {         "HOOKNAME": {             "scope": "DIRNAME",             "apparmor": "apparmor.json"         }     },    "name": "PACKAGENAME"     ... } The tool should look in     DIRNAME/PACKAGENAME_HOOKNAME.ini for the the ini file. It is currently looking in DIRNAME/PACKAGENAME.ini which is incorrect.
2014-07-30 16:17:19 Pete Woods branch linked lp:~pete-woods/click-reviewers-tools/wrong-scope-ini-path
2014-07-30 16:45:57 Pete Woods description Following the apparmor policy updates a little while ago, scopes are now named after the hook short ID. For a scope package "package-name" with a hook "hook-name" to the directory "dir-name". manifest.json: {     ...     "hooks": {         "HOOKNAME": {             "scope": "DIRNAME",             "apparmor": "apparmor.json"         }     },    "name": "PACKAGENAME"     ... } The tool should look in     DIRNAME/PACKAGENAME_HOOKNAME.ini for the the ini file. It is currently looking in DIRNAME/PACKAGENAME.ini which is incorrect. Following the apparmor policy updates a little while ago, scopes are now named after the hook short ID. For a scope package "package-name" with a hook "hook-name" to the directory "dir-name". manifest.json: {     ...     "hooks": {         "HOOKNAME": {             "scope": "DIRNAME",             "apparmor": "apparmor.json"         }     },    "name": "PACKAGENAME"     ... } The tool should look in     DIRNAME/PACKAGENAME_HOOKNAME.ini for the the ini file. It is currently looking in     DIRNAME/PACKAGENAME.ini which is incorrect. Additionally, the validation rules for the ini file itself are incomplete and incorrect. Please see the documentation at http://bazaar.launchpad.net/~unity-team/unity-scopes-api/trunk/view/head:/CONFIGFILES
2014-07-31 09:18:52 Daniel Holbach click-reviewers-tools: status New Fix Committed
2014-07-31 09:18:52 Daniel Holbach click-reviewers-tools: assignee Pete Woods (pete-woods)
2014-07-31 09:19:05 Daniel Holbach tags scope-dev
2014-08-27 14:24:24 Daniel Holbach click-reviewers-tools: status Fix Committed Fix Released
2014-08-27 14:57:21 Launchpad Janitor branch linked lp:ubuntu/click-reviewers-tools