Sounds like it's this issue (introduced in 0.10, fixed in 0.13):
https://bugs.launchpad.net/mir/+bug/1415321
It has a regression test now so once everything is on 0.13 it won't
happen again.
On 27/05/15 16:49, Alan Griffiths wrote:
Hi Robert,
Is "release breakage" t
Hi Robert,
Is "release breakage" the same problem with landing Mir-0.13.x on wily
that I was discussing with kgunn yesterday?
AIUI the problem was an unexpected dependant of libmircommon. I believe
clients should not be linking against libmircommon (only libmirclient),
but we had some
Hi all,
I'm trying to track the release breakage. It seems many required downstream
branches need to land, and some updates need to be made to qtubuntu and
gst-plugins-bad.
The release should have failed in the Silo but I am told the underlying
cause relates to downstreams building agains
