[MIR] unity-system-compositor
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
unity-system-compositor (Ubuntu) |
Fix Released
|
Undecided
|
Unassigned |
Bug Description
Note that a much older version of unity-system-
https:/
[Availability]
* Available in universe
[Rationale]
* This package is the system compositor for our convergence effort
* Used by default on phablet images and in the Unity8 session on the desktop
[Security]
* No known security issues at this time
* A security review is recommended. The package had been reviewed in the past by the security team for use on the phone, but it has changed significantly since then.
[Quality assurance]
* This package has unit and integration tests that run with each package build
* CI is used during development
[Dependencies]
* All dependencies are in main
* It 'Suggests' repowerd which already has a MIR:
https:/
[Standards compliance]
* Follows FHS and Debian Policy.
* This package uses cmake.
[Maintenance]
* This package is maintained by Canonical and actively in use on the phone images
* mir-development
Changed in unity-system-compositor (Ubuntu): | |
status: | Fix Committed → Fix Released |
tags: | added: unity8-desktop |
- android-properties should be a Build-Dep in arm64, right?
- Is ubuntu-desktop-mir needed anymore?
- This builds its autopilot package with python2... Didn't we switch to python3 for all autopilot usage? I'd think it should build-dep on dh-python, drop the python2 build-deps, and use --with python3 instead of --with python2 (and switch python:Depends to python3:Depends, depend on python3-autopilot instead of python-autopilot, etc).
- Can we subscribe phablet-team, ubuntu- phonedations- bugs, or unity-api-team to LP bugs? Whichever you think is most appropriate. We just want a standard team on the hook for bugs.
- Does anyone know if we can drop the "sleep .1" from the wrapper script? I worry the answer is no, and that we will never drop it.
- It seems like there are an awful lot of crashers in the bug list. But since this MIR is clearing the way to slowly experiment with phasing this onto Desktops instead of an immediate switch, we can get those down over time.