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.
** Also affects: mesa (Ubuntu)
Importance: Undecided
Status: New
** Changed in: mesa (Ubuntu)
Status: New => Won't Fix
** Description changed:
- Mir/Mesa have a dependency cycle so cannot be upgraded.
+ 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.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to mesa in Ubuntu.
https://bugs.launchpad.net/bugs/1192908
Title:
Mir/Mesa packaging have a dependency cycle so cannot be upgraded
Status in Mir:
New
Status in “mesa” package in Ubuntu:
Won't Fix
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.
To manage notifications about this bug go to:
https://bugs.launchpad.net/mir/+bug/1192908/+subscriptions
--
Mailing list: https://launchpad.net/~desktop-packages
Post to : [email protected]
Unsubscribe : https://launchpad.net/~desktop-packages
More help : https://help.launchpad.net/ListHelp
