Merge lp:~townsend/libertine/unset_dconf into lp:libertine
Proposed by
Christopher Townsend
Status: | Merged | ||||
---|---|---|---|---|---|
Approved by: | Stephen M. Webb | ||||
Approved revision: | 165 | ||||
Merged at revision: | 165 | ||||
Proposed branch: | lp:~townsend/libertine/unset_dconf | ||||
Merge into: | lp:libertine | ||||
Diff against target: |
15 lines (+5/-0) 1 file modified
python/libertine/ChrootContainer.py (+5/-0) |
||||
To merge this branch: | bzr merge lp:~townsend/libertine/unset_dconf | ||||
Related bugs: |
|
Reviewer | Review Type | Date Requested | Status |
---|---|---|---|
Stephen M. Webb (community) | Approve | ||
Libertine CI Bot | continuous-integration | Approve | |
Review via email: mp+284187@code.launchpad.net |
Commit message
Workaround issue where a custom dconf profile is on a machine. Of course the profile is not in the chroot, so it messes up some applications.
To post a comment you must log in.
PASSED: Continuous integration, rev:165 /jenkins. canonical. com/libertine/ job/libertine- ci-verify- mp/104/ /jenkins. canonical. com/libertine/ job/libertine- ci-update- mp/1001/ console
https:/
Executed test runs:
None: https:/
Click here to trigger a rebuild: /jenkins. canonical. com/libertine/ job/libertine- ci-verify- mp/104/ rebuild
https:/