** Description changed: [Impact] Snap development using Mir has been using the "stable phone overlay" PPA which is both inconvenient and a legacy of the cancelled Unity8 project. It would greatly simplify things if Mir were updated in the Xenial archive. [Test Case] Build a Mir client snap (e.g. lp:~albaguirre/+snap/mir-client-demos) against "Primary Ubuntu Archive" and deploy as described in https://developer.ubuntu.com/en/snappy/guides/mir-snaps/ Expected: the client apps start and are visible on screen Actual: the client apps don't start and are not visible on screen [Regression Potential] Mir has two categories of dependent project: 1 Unity8 and unity-system-compositor "server" packages 2 toolkits and other "clients" of Mir "Server" packages from the archive will stop working in the LTS as they will continue using the earlier libmirserver.so.38 (from Mir 0.21) which doesn't work with the libmirclient.so.9 from Mir 0.26. This is unimportant as these packages were provided as an "early experience", not for serious use. "Client" packages are dependent only on libmirclient.so.9 which is ABI stable. The principle type of regression would be FTBFS where APIs have been deprecated in 0.26. The linked 0.26.3 release has these deprecations disabled for 16.04. The packages are available in silo: https://bileto.ubuntu.com/#/ticket/2736 notes: A recursive search or rdependencies identifies the following packages in category 1: camera-app-autopilot gallery-app-autopilot indicator-network-autopilot indicators-client qtdeclarative5-qtmir-plugin qtmir-android qtmir-desktop qtmir-tests ubuntu-desktop-mir ubuntu-experience-tests ubuntu-pocket-desktop ubuntu-push-autopilot ubuntu-touch ubuntu-touch-session unity8 unity8-autopilot unity8-desktop-session-mir unity-scope-click-autopilot unity-system-compositor unity-system-compositor-autopilot Anyone wanting these packages should switch to the "unity8-desktop- session" preview package in 17.04 where they are far more functional. + + [Alternatives] + If we want to keep everything working in Xenial, we *could* bump the libmirclient SONAME to libmirclient.so.10. This would result in libmirclient9 being NBS, but continuing to work against the Mir servers available in 16.04 (until and unless they are rebuilt).
-- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1685186 Title: [SRU] Mir needs to be updated to 0.26 in 16.04LTS To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mir/+bug/1685186/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
