Mir/Mesa packaging have a dependency cycle so neither can build
Bug #1192908 reported by
Daniel van Vugt
This bug affects 2 people
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Mir |
Fix Released
|
Critical
|
Daniel van Vugt | ||
mesa (Ubuntu) |
Won't Fix
|
Medium
|
Unassigned | ||
mir (Ubuntu) |
New
|
Undecided
|
Unassigned |
Bug Description
Mir/Mesa have a dependency cycle so cannot build if there are any significant changes in one (like a soname/ABI bump).
Mesa depends on mirclient
mirserver depends on Mesa
what makes it a cycle is that mirclient and mirserver are a single source package. So if anything changes (like libmirclient0 changing to libmirclient1) then we're stuck and can't rebuild anything. Not sure which chicken or egg came first and how we made it work originally.
Related branches
lp:~vanvugt/mir/fix-1192908
- Chris Halse Rogers: Approve
- Robert Ancell: Approve
- Alan Griffiths: Needs Fixing
- PS Jenkins bot (community): Approve (continuous-integration)
-
Diff: 27 lines (+17/-0)1 file modifiedsrc/client/CMakeLists.txt (+17/-0)
summary: |
- Mir/Mesa have a dependency cycle so cannot be upgraded + Mir/Mesa packaging have a dependency cycle so cannot be upgraded |
Changed in mir: | |
status: | New → In Progress |
Changed in mir: | |
importance: | Undecided → High |
Changed in mir: | |
importance: | High → Critical |
Changed in mir: | |
milestone: | 0.0.4 → 0.0.5 |
Changed in mir: | |
status: | Fix Committed → Fix Released |
To post a comment you must log in.
You might be able to work around the problem by building Mir against vanilla Mesa (which does not depend on Mir). That might work, as a slow and painful workaround.