unity-system-compositor FTBFS on trusty against new Mir (libmirserver8)
Bug #1244131 reported by
Timo Jyrinki
This bug affects 1 person
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| Mir |
Invalid
|
Critical
|
Unassigned | ||
| Unity System Compositor |
Fix Released
|
Critical
|
Michael Terry | ||
Bug Description
/build/
This prevents publishing of the mir stack.
Looks like https:/
Related branches
lp:~mterry/unity-system-compositor/mir-fixes
- Timo Jyrinki (community): Approve
- PS Jenkins bot (community): Needs Fixing (continuous-integration)
- Daniel van Vugt: Approve
- Robert Ancell: Approve
-
Diff: 55 lines (+10/-6)2 files modifieddebian/control (+1/-1)
src/system_compositor.cpp (+9/-5)
| description: | updated |
| Changed in mir: | |
| importance: | Undecided → Critical |
| Changed in unity-system-compositor: | |
| status: | New → In Progress |
| assignee: | nobody → Michael Terry (mterry) |
| Changed in mir: | |
| status: | New → Invalid |
| Changed in unity-system-compositor: | |
| status: | In Progress → Fix Committed |
| summary: |
- unity-system-compositor FTBFS on trusty against new Mir + unity-system-compositor FTBFS on trusty against new Mir (libmirserver8) |
Revision history for this message
| Timo Jyrinki (timo-jyrinki) wrote | #1 |
| Changed in unity-system-compositor: | |
| status: | Fix Committed → Fix Released |
To post a comment you must log in.
This was fixed to fix build against libmirserver8, but unfortunately we now have libmirserver9 already, see bug #1244192