← Back to team overview

desktop-packages team mailing list archive

[Bug 1509005] Re: [regression] mir-client-platform-mesa-dev pkg-config file dropped

 

Hello Matthias, or anyone else affected,

Accepted xorg-server into wily-proposed. The package will build now and
be available at https://launchpad.net/ubuntu/+source/xorg-
server/2:1.17.2-1ubuntu9.1 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 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!

** Changed in: xorg-server (Ubuntu Wily)
       Status: Confirmed => Fix Committed

** Tags added: verification-needed

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

Title:
  [regression] mir-client-platform-mesa-dev pkg-config file dropped

Status in Mir:
  Fix Committed
Status in mesa package in Ubuntu:
  Fix Released
Status in mir package in Ubuntu:
  Triaged
Status in xorg-server package in Ubuntu:
  Fix Released
Status in mesa source package in Wily:
  Confirmed
Status in mir source package in Wily:
  Confirmed
Status in xorg-server source package in Wily:
  Fix Committed

Bug description:
  the mir-client-platform-mesa-dev pkg-config file was dropped in wily,
  leading to build errors for such optional packages like mesa and xorg-
  server.

  Even if you have a feature freeze exception, you shouldn't break
  existing API's after feature freeze.

To manage notifications about this bug go to:
https://bugs.launchpad.net/mir/+bug/1509005/+subscriptions