This bug was fixed in the package xorg-server - 2:1.18.3-1ubuntu2.3

---------------
xorg-server (2:1.18.3-1ubuntu2.3) xenial; urgency=medium

  [ Timo Aaltonen ]
  * control: Add Conflicts/Replaces on xserver-xorg-video-glamoregl.
    (LP: #1574320)

  [ Ɓukasz 'sil2100' Zemczak ]
  * debian/control, debian/rules:
    - Build xmir for arm64 (LP: #1604851).

 -- Timo Aaltonen <tjaal...@debian.org>  Thu, 21 Jul 2016 08:27:07 +0300

** Changed in: xorg-server (Ubuntu Xenial)
       Status: Fix Committed => Fix Released

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to xorg-server in Ubuntu.
https://bugs.launchpad.net/bugs/1604851

Title:
  Missing arm64 xmir binaries

Status in Canonical System Image:
  In Progress
Status in xorg-server package in Ubuntu:
  Fix Released
Status in xorg-server source package in Xenial:
  Fix Released

Bug description:
  [Impact]

  Currently we are not building xmir packages for arm64 as there was no
  consumer for such binaries. With the current xenial plans and a
  potential switch to arm64, we now need to provide arm64 binaries for
  testing our Ubuntu Touch arm64 images (which currently cannot be built
  without xmir on arm64). This is critical and crucial for our Ubuntu
  Touch switch to xenial.

  [Test Case]

  Making sure that xmir builds on arm64. Currently no other testing
  means are easily available, we need to have xmir building at all to
  build our first arm64 rootfs and then dive into testing.

  [Regression Potential]

  No risk potential on existing platforms as it only involves packaging
  changes enabling the new architecture for xmir. No source changes
  required.

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1604851/+subscriptions

-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to     : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

Reply via email to