Merge lp:~ken-vandine/autopilot/depends_for_gsettings into lp:autopilot
| Status: | Merged |
|---|---|
| Merged at revision: | 566 |
| Proposed branch: | lp:~ken-vandine/autopilot/depends_for_gsettings |
| Merge into: | lp:autopilot |
| Diff against target: |
19 lines (+2/-0) 1 file modified
debian/control (+2/-0) |
| To merge this branch: | bzr merge lp:~ken-vandine/autopilot/depends_for_gsettings |
| Related bugs: |
| Reviewer | Review Type | Date Requested | Status |
|---|---|---|---|
| PS Jenkins bot | continuous-integration | Approve on 2015-07-22 | |
| Iain Lane (community) | Needs Fixing on 2015-07-22 | ||
| Max Brustkern (community) | 2015-07-22 | Approve on 2015-07-22 | |
|
Review via email:
|
|||
Commit Message
added depends for libglib2.0-bin
Description of the Change
added depends for libglib2.0-bin
This is needed to fix autopkgtests that are now failing because of the recent gsettings addition.
| Ken VanDine (ken-vandine) wrote : | # |
- 567. By Ken VanDine on 2015-07-22
-
Depend on ubuntu-
keyboard- data for the gsettings schema
| Iain Lane (laney) wrote : | # |
Can we please instead make this opt in with a soft depends for those tests/projects that need it? I don't see why all users of autopilot should be forced to do things to work around problems with the Ubuntu keyboard that may not remotely concern them.
And please let's use the proper API for interacting with gsettings instead of an administration tool.
| PS Jenkins bot (ps-jenkins) wrote : | # |
PASSED: Continuous integration, rev:567
http://
Executed test runs:
SUCCESS: http://
deb: http://
SUCCESS: http://
deb: http://
SUCCESS: http://
deb: http://
UNSTABLE: http://
UNSTABLE: http://
SUCCESS: http://
deb: http://
SUCCESS: http://
Click here to trigger a rebuild:
http://
| Christopher Lee (veebers) wrote : | # |
> Can we please instead make this opt in with a soft depends for those
> tests/projects that need it? I don't see why all users of autopilot should be
> forced to do things to work around problems with the Ubuntu keyboard that may
> not remotely concern them.
>
> And please let's use the proper API for interacting with gsettings instead of
> an administration tool.
These concerns should be address with this branch: https:/

This looks good to me. I'll see what we can do about getting a release.