[SRU] Mir needs to be updated to 0.26 in 16.04LTS

Yeah I agree. Mir lives on in a new form, and that should be without PPAs. Thus the archive should be updated if anything Mir-related is desired on xenial.

Status changed to 'Confirmed' because the bug affects multiple users.

Keeping notes here for ease of reference. The rdepends of libmirclient are:

libmirclient9
Reverse Depends:
  Depends: ubuntu-application-api3-desktop (>= 0.19.0+16.04.20160128)
  Depends: xmir-hwe-16.04 (>= 0.21.0+16.04.20160330)
  Depends: xmir (>= 0.21.0+16.04.20160330)
  Depends: libgtk-3-0 (>= 0.21.0+16.04.20160330)
  Depends: xmir (>= 0.20.3+16.04.20160322)
  Depends: url-dispatcher (>= 0.17.1+16.04.20151105.1)
  Depends: unity-system-compositor (>= 0.20.2+16.04.20160307)
  Depends: ubuntu-system-settings-online-accounts (>= 0.20.2+16.04.20160307)
  Depends: ubuntu-application-api3-touch (>= 0.19.0+16.04.20160128)
  Depends: qtdeclarative5-qtmir-plugin (>= 0.20.3+16.04.20160322)
  Depends: ubuntu-app-test (>= 0.17.1+16.04.20151105.1)
  Depends: qtubuntu-desktop (>= 0.20.2+16.04.20160307)
  Depends: qtubuntu-android (>= 0.20.2+16.04.20160307)
  Depends: qtmir-desktop (>= 0.20.3+16.04.20160322)
  Depends: qtmir-android (>= 0.20.3+16.04.20160322)
  Depends: libubuntu-app-launch2 (>= 0.17.1+16.04.20151105.1)
  Depends: pay-service (>= 0.20.2+16.04.20160307)
  Depends: mir-utils (>= 0.21.0+16.04.20160330)
  Depends: mir-test-tools (>= 0.21.0+16.04.20160330)
  Depends: mir-demos (>= 0.21.0+16.04.20160330)
  Depends: mir-client-platform-mesa5 (>= 0.21.0+16.04.20160330)
  Depends: mir-android-diagnostics (>= 0.21.0+16.04.20160330)
  Depends: libtrust-store2 (>= 0.18.1+16.04.20160115)
  Depends: glmark2-es2-mir (>= 0.14.0+15.10.20150701)
  Depends: glmark2-mir (>= 0.14.0+15.10.20150701)
  Depends: libmirserver38 (>= 0.21.0+16.04.20160330)
  Depends: libmirclient-dev (= 0.21.0+16.04.20160330-0ubuntu1)
  Depends: libgtk-3-0 (>= 0.20.2+16.04.20160307)

Removing the Mir packages:

glmark2-es2-mir
glmark2-mir
libgtk-3-0
libtrust-store2
libubuntu-app-launch2
pay-service
qtubuntu-android
qtubuntu-desktop
ubuntu-application-api3-desktop
ubuntu-application-api3-touch
ubuntu-app-test
ubuntu-system-settings-online-accounts
unity-system-compositor
url-dispatcher
xmir

These are the packages that may FTBFS if 0.26 is pushed to the store

Hello Alan, or anyone else affected,

Accepted mir into xenial-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/mir/0.26.3+16.04.20170510-0ubuntu1 in a few hours, and then in the -proposed repository.

Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed.Your feedback will aid us getting this update out to other Ubuntu users.

If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, and change the tag from verification-needed to verification-done. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed. In either case, details of your testing will help us make a better decision.

Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance!

This works fine on a AMD64 desktop

Does the intended for the mir snaps too:

lp:~saviq/mir-kiosk-apps/+git/mir-kiosk-apps/+merge/324179
lp:~saviq/mir-kiosk/+git/mir-kiosk/+merge/324180
lp:~saviq/mir-libs-snap/+git/mir-libs-snap/+merge/324197

We've updated, built and tested the snaps comprising the "kiosk" stack [1]. Everything is in order.

[1] https://developer.ubuntu.com/en/snappy/guides/mir-snaps/

Tested version 0.26.3+16.04.20170510-0ubuntu1

I've set this to verification-failed to prevent the accidental release of the package because these changes do not seem to exist in Artful, a requirement of the SRU process, and the version number of the package in xenial-proposed is greater than the version of the package in releases newer than Ubuntu 16.04.

This bug was fixed in the package mir - 0.26.3+17.10.20170526.3-0ubuntu1

---------------
mir (0.26.3+17.10.20170526.3-0ubuntu1) artful; urgency=medium

  [ Daniel van Vugt ]
  * New upstream release 0.26.3 (https://launchpad.net/mir/+milestone/0.26.3)
    - Enhancements:
      . Make deprecations optional (and default to off for builds on 16.04 LTS)
      . Added support for building on Ubuntu 17.10 artful.
    - Bugs fixed:
      . Mir needs to be updated to 0.26 in 16.04LTS (LP: #1685186)
      . unity-system-compositor crashed with SIGSEGV in
        libinput_device_config_accel_is_available() from
        libinput_device_config_accel_set_speed() from
        mir::input::evdev::LibInputDevice::apply_settings() (LP: #1672955)
      . Please transition to Boost 1.62 (LP: #1675138)
      . Mir sending key repeat events continually to nested shell after VT
        switch (causes Unity8 lockup for a while) (LP: #1675357)
      . mir_demo_standalone_render_overlays fails to link (LP: #1677239)

 -- Alan Griffiths <email address hidden> Fri, 26 May 2017 16:57:20 +0000

Added Zesty and Yakkety as they need to have at least the version in Xenial.

For Zesty this is a bugfix update, on Yakkety it has the same effect as on Xenial (of making some "early experience" downstreams a little less useful).

Set back to verification-needed as we now have the binaries for all the supported releases

Hello Alan, or anyone else affected,

Accepted mir into xenial-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/mir/0.26.3+16.04.20170605-0ubuntu1 in a few hours, and then in the -proposed repository.

Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed.Your feedback will aid us getting this update out to other Ubuntu users.

If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, and change the tag from verification-needed to verification-done. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed. In either case, details of your testing will help us make a better decision.

Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance!

Hello Alan, or anyone else affected,

Accepted mir into yakkety-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/mir/0.26.3+16.10.20170605-0ubuntu1 in a few hours, and then in the -proposed repository.

Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed.Your feedback will aid us getting this update out to other Ubuntu users.

If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, and change the tag from verification-needed to verification-done. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed. In either case, details of your testing will help us make a better decision.

Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance!

Hello Alan, or anyone else affected,

Accepted mir into zesty-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/mir/0.26.3+17.04.20170605-0ubuntu1 in a few hours, and then in the -proposed repository.

Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed.Your feedback will aid us getting this update out to other Ubuntu users.

If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, and change the tag from verification-needed to verification-done. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed. In either case, details of your testing will help us make a better decision.

Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance!

Tested:
xenial: 0.26.3+16.04.20170605-0ubuntu1
yakkety: 0.26.3+16.10.20170605-0ubuntu1
zesty: 0.26.3+17.04.20170605-0ubuntu1

All is fine.

The verification of the Stable Release Update for mir has completed successfully and the package has now been released to -updates. Subsequently, the Ubuntu Stable Release Updates Team is being unsubscribed and will not receive messages about this bug report. In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions.

This bug was fixed in the package mir - 0.26.3+16.10.20170605-0ubuntu1

---------------
mir (0.26.3+16.10.20170605-0ubuntu1) yakkety; urgency=medium

  [ Daniel van Vugt ]
  * New upstream release 0.26.3 (https://launchpad.net/mir/+milestone/0.26.3)
    - Enhancements:
      . Make deprecations optional (and default to off for builds on 16.04 LTS)
      . Added support for building on Ubuntu 17.10 artful.
    - Bugs fixed:
      . Mir needs to be updated to 0.26 in 16.04LTS (LP: #1685186)
      . unity-system-compositor crashed with SIGSEGV in
        libinput_device_config_accel_is_available() from
        libinput_device_config_accel_set_speed() from
        mir::input::evdev::LibInputDevice::apply_settings() (LP: #1672955)
      . Please transition to Boost 1.62 (LP: #1675138)
      . Mir sending key repeat events continually to nested shell after VT
        switch (causes Unity8 lockup for a while) (LP: #1675357)
      . mir_demo_standalone_render_overlays fails to link (LP: #1677239)

 -- Michał Sawicz <email address hidden> Mon, 05 Jun 2017 13:46:05 +0000

This bug was fixed in the package mir - 0.26.3+16.04.20170605-0ubuntu1

---------------
mir (0.26.3+16.04.20170605-0ubuntu1) xenial; urgency=medium

  [ Daniel van Vugt ]
  * New upstream release 0.26.3 (https://launchpad.net/mir/+milestone/0.26.3)
    - Enhancements:
      . Make deprecations optional (and default to off for builds on 16.04 LTS)
      . Added support for building on Ubuntu 17.10 artful.
    - Bugs fixed:
      . Mir needs to be updated to 0.26 in 16.04LTS (LP: #1685186)
      . unity-system-compositor crashed with SIGSEGV in
        libinput_device_config_accel_is_available() from
        libinput_device_config_accel_set_speed() from
        mir::input::evdev::LibInputDevice::apply_settings() (LP: #1672955)
      . Please transition to Boost 1.62 (LP: #1675138)
      . Mir sending key repeat events continually to nested shell after VT
        switch (causes Unity8 lockup for a while) (LP: #1675357)
      . mir_demo_standalone_render_overlays fails to link (LP: #1677239)

 -- Michał Sawicz <email address hidden> Mon, 05 Jun 2017 11:01:05 +0000

This bug was fixed in the package mir - 0.26.3+17.04.20170605-0ubuntu1

---------------
mir (0.26.3+17.04.20170605-0ubuntu1) zesty; urgency=medium

  [ Daniel van Vugt ]
  * New upstream release 0.26.3 (https://launchpad.net/mir/+milestone/0.26.3)
    - Enhancements:
      . Make deprecations optional (and default to off for builds on 16.04 LTS)
      . Added support for building on Ubuntu 17.10 artful.
    - Bugs fixed:
      . Mir needs to be updated to 0.26 in 16.04LTS (LP: #1685186)
      . unity-system-compositor crashed with SIGSEGV in
        libinput_device_config_accel_is_available() from
        libinput_device_config_accel_set_speed() from
        mir::input::evdev::LibInputDevice::apply_settings() (LP: #1672955)
      . Please transition to Boost 1.62 (LP: #1675138)
      . Mir sending key repeat events continually to nested shell after VT
        switch (causes Unity8 lockup for a while) (LP: #1675357)
      . mir_demo_standalone_render_overlays fails to link (LP: #1677239)

 -- Michał Sawicz <email address hidden> Mon, 05 Jun 2017 11:04:47 +0000