Merge lp:~khadgaray/unity-lens-applications/fix-lockdown into lp:unity-lens-applications
| Status: | Needs review | ||||
|---|---|---|---|---|---|
| Proposed branch: | lp:~khadgaray/unity-lens-applications/fix-lockdown | ||||
| Merge into: | lp:unity-lens-applications | ||||
| Diff against target: |
16 lines (+6/-0) 1 file modified
src/daemon.vala (+6/-0) |
||||
| To merge this branch: | bzr merge lp:~khadgaray/unity-lens-applications/fix-lockdown | ||||
| Related bugs: |
|
| Reviewer | Review Type | Date Requested | Status |
|---|---|---|---|
| PS Jenkins bot | continuous-integration | Needs Fixing on 2013-04-13 | |
| Didier Roche | Needs Fixing on 2012-07-05 | ||
| Mikkel Kamstrup Erlandsen (community) | 2012-07-03 | Needs Information on 2012-07-04 | |
|
Review via email:
|
|||
Description of the Change
Allows an admin to disable command run dialog based on gnome security policies.
| Ritesh Khadgaray (khadgaray) wrote : | # |
> This adds a hard runtime dep on the org.gnome.
> this imply a new dependency for the package as well?
Unity already depends on this via libgnome-
-- ritz
| Didier Roche (didrocks) wrote : | # |
I would rather the check happening when the lens is started and then listening to the key changing than after you did a search and ready to activate it.
In that case, we should display a friendly message to the user rather than afterwards :)
Also yeah, as told on IRC, the dependency should be specified directly. And it needs tests ;)
| PS Jenkins bot (ps-jenkins) wrote : | # |
FAILED: Continuous integration, rev:287
No commit message was specified in the merge proposal. Click on the following link and set the commit message (if you want a jenkins rebuild you need to trigger it yourself):
https:/
http://
Executed test runs:
FAILURE: http://
FAILURE: http://
FAILURE: http://
Click here to trigger a rebuild:
http://
Unmerged revisions
- 287. By Ritesh Khadgaray on 2012-07-03
-
add lockdown support to disable commandline (LP# 813895)

This adds a hard runtime dep on the org.gnome. desktop. lockdown schema. Does this imply a new dependency for the package as well?