>From my end, I don't know of blockers for the UAP-without-Mir upload. However, I would like to just take this moment to note that I haven't heard any talk of actually bumping the UAP interface number. Which means that by removing libraries, we're breaking our snap interface contract -- one we've released into the stable channel.
Now that's fine, teething pains and all that. And maybe we don't expect anyone to seriously be using the Mir libraries from UAP. (Though someone might be...) Has the UAP team considered what the Right Thing would look like here? At least as a thought experiment for next time. But maybe even if it's easy, we can do it here too. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unity8 in Ubuntu. https://bugs.launchpad.net/bugs/1663048 Title: libmirclient in snaps gets out of sync with archive Status in Canonical System Image: Confirmed Status in Ubuntu App Platform: In Progress Status in unity8 package in Ubuntu: In Progress Status in unity8-desktop-session package in Ubuntu: Fix Released Bug description: Because we directly include mir client libraries in the platform (due to a dependency of qtubuntu), when the mir interface is revised we get out of sync. The mir team publishes a mir-libs snap that tracks these changes and exposes a mir-libs content interface. We should investigate if that can be used transparently by apps connected to the platform. as of this report they are out of sync. To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1663048/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
