Merge lp:~ubuntu-mate-dev/ubiquity/mate-compatibility into lp:ubiquity
| Status: | Merged |
|---|---|
| Approved by: | Mathieu Trudel-Lapierre on 2016-06-22 |
| Approved revision: | 6451 |
| Merged at revision: | 6451 |
| Proposed branch: | lp:~ubuntu-mate-dev/ubiquity/mate-compatibility |
| Merge into: | lp:ubiquity |
| Diff against target: |
35 lines (+8/-8) 1 file modified
bin/ubiquity-dm (+8/-8) |
| To merge this branch: | bzr merge lp:~ubuntu-mate-dev/ubiquity/mate-compatibility |
| Related bugs: |
| Reviewer | Review Type | Date Requested | Status |
|---|---|---|---|
| Mathieu Trudel-Lapierre | 2016-06-13 | Approve on 2016-06-22 | |
| Ubuntu Sponsors Team | 2016-06-13 | Pending | |
| Canonical Foundations Team | 2016-06-13 | Pending | |
|
Review via email:
|
|||
Description of the Change
The Ubuntu MATE seeds/meta-packages have been modified to follow Recommends. This means that unity-control-
This merge proposal changes the order the settings daemons are attempted to be started in ubiquity-dm. mate-settings-
| Mathieu Trudel-Lapierre (cyphermox) wrote : | # |
Sounds like there is decent justification for having the change after all; approved.
FTR; there is a complex chain of dependencies from wanting to land shotwell, which suggests some account-plugin-* packages which in turn will eventually depend on u-s-d magic. Having u-s-d in the image would make it loaded first by ubiquity-dm, since it's evaluated first.


Seems like whatever pulls in u-s-d and/or g-s-d should be fixed (add an alternate Depends on the right settings-daemon, instead of reordering things here).
If some other package Depends on u-s-d, it probably already also depends on u-s-d | g-s-d. In this sense, it makes sense to add "| m-s-d" rather than modifying the order in which things are loaded here.