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 misplaced entry points: $ apt-cache rdepends libmircommon3 | grep -v "\(libmir\|\bmir-\)" Reverse Depends: unity-system-compositor qtubuntu-desktop qtubuntu-android qtmir-desktop qtmir-android qtdeclarative5-qtmir-plugin We had unity-system-compositor and qtmir in the silo but missed qtubuntu (which needs some event API renames to compile). The qtubuntu branch below is what I would have added to the silo had (I not reached EOD). kgunn said he and camako would pick that up but I haven't yet seen any sign of that, so I'm wondering what, if anything, happened next. Are you dealing with it? I don't see platform-api in the above list, so is that a different, or additional, problem? (It should be updated to reflect API changes, but it should be installable and not block landing.) Alan On 26/05/15 22:24, Robert Carr wrote: > 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 against old versions > of mircommon > > Platform-api: This needs to land > https://code.launchpad.net/~mir-team/platform-api/delete-deprecations/+merge/254170 > <https://code.launchpad.net/%7Emir-team/platform-api/delete-deprecations/+merge/254170> > > Qtubuntu: Needed a new branch to track the vanity event renamings > https://code.launchpad.net/~mir-team/qtubuntu/track-mir-deprecations/+merge/260214 > <https://code.launchpad.net/%7Emir-team/qtubuntu/track-mir-deprecations/+merge/260214> > > Gst-plugins-bad: > adding-mir-sink-and-android-media-over-hybris-support.patch > > A debian patch uses the old ubuntu_application_ui functions to create > a window. I'm told this has been broken since the surface flinger > transition anyway so I think we should delete it. I'm trying to find > someone who knows something about this. > > > >
-- Mir-devel mailing list Mir-devel@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/mir-devel
