Merge lp:~aacid/unity8/unity-scope-tool-fixes into lp:unity8
| Status: | Merged |
|---|---|
| Approved by: | Andrea Cimitan on 2016-02-26 |
| Approved revision: | 2206 |
| Merged at revision: | 2263 |
| Proposed branch: | lp:~aacid/unity8/unity-scope-tool-fixes |
| Merge into: | lp:unity8 |
| Diff against target: |
38 lines (+2/-9) 2 files modified
debian/control (+2/-1) qml/ScopeTool.qml (+0/-8) |
| To merge this branch: | bzr merge lp:~aacid/unity8/unity-scope-tool-fixes |
| Related bugs: |
| Reviewer | Review Type | Date Requested | Status |
|---|---|---|---|
| Andrea Cimitan (community) | Approve on 2016-02-26 | ||
| PS Jenkins bot | continuous-integration | Needs Fixing on 2016-02-25 | |
| Unity8 CI Bot | continuous-integration | Approve on 2016-02-25 | |
| Pete Woods (community) | Approve on 2016-02-25 | ||
| dobey (community) | 2016-02-25 | Approve on 2016-02-25 | |
|
Review via email:
|
|||
Commit Message
Minor fixes for unity-scope-tool
* Make the package install things better by making unity8-private pull the gsettings and multimedia deps it has
* Remove unneeded background code
Description of the Change
* Are there any related MPs required for this MP to build/function as expected?
No
* Did you perform an exploratory manual test run of your code change and any related functionality?
Yes
* Did you make sure that your branch does not contain spurious tags?
Yes
* If you changed the packaging (debian), did you subscribe the ubuntu-unity team to this MP?
N/A
* If you changed the UI, has there been a design review?
N/A
| Unity8 CI Bot (unity8-ci-bot) wrote : | # |
PASSED: Continuous integration, rev:2206
https:/
Executed test runs:
SUCCESS: https:/
SUCCESS: https:/
SUCCESS: https:/
SUCCESS: https:/
SUCCESS: https:/
SUCCESS: https:/
SUCCESS: https:/
deb: https:/
SUCCESS: https:/
deb: https:/
SUCCESS: https:/
deb: https:/
SUCCESS: https:/
deb: https:/
SUCCESS: https:/
deb: https:/
SUCCESS: https:/
deb: https:/
Click here to trigger a rebuild:
https:/
| PS Jenkins bot (ps-jenkins) wrote : | # |
FAILED: Continuous integration, rev:2206
http://
Executed test runs:
UNSTABLE: http://
FAILURE: http://
SUCCESS: http://
SUCCESS: http://
SUCCESS: http://
SUCCESS: http://
SUCCESS: http://
SUCCESS: http://
UNSTABLE: http://
SUCCESS: http://
deb: http://
SUCCESS: http://
FAILURE: http://
SUCCESS: http://
deb: http://
SUCCESS: http://
Click here to trigger a rebuild:
http://
| Andrea Cimitan (cimi) wrote : | # |
* Did you perform an exploratory manual test run of the code change and any related functionality?
dobey and pete did
* Did CI run pass? If not, please explain why.
ap
* Did you make sure that the branch does not contain spurious tags?
y

Looks good to me, thanks!