[Bug 1253041] Re: lts-saucy enablement in precise

Maarten Lankhorst maarten.lankhorst at canonical.com
Thu Jan 2 11:34:06 UTC 2014


Quantal and raring still boot correctly. :)

** Tags removed: verification-needed
** Tags added: verification-done-precise verification-done-quantal verification-done-raring

-- 
You received this bug notification because you are a member of Ubuntu
Foundations Bugs, which is subscribed to libdrm in Ubuntu.
https://bugs.launchpad.net/bugs/1253041

Title:
  lts-saucy enablement in precise

Status in “libdrm” package in Ubuntu:
  Invalid
Status in “mesa” package in Ubuntu:
  Invalid
Status in “pixman” package in Ubuntu:
  Invalid
Status in “libdrm” source package in Precise:
  Fix Committed
Status in “mesa” source package in Precise:
  Fix Committed
Status in “pixman” source package in Precise:
  Fix Committed
Status in “libdrm” source package in Quantal:
  Fix Committed
Status in “mesa” source package in Quantal:
  Invalid
Status in “pixman” source package in Quantal:
  Fix Committed
Status in “libdrm” source package in Raring:
  Fix Committed
Status in “mesa” source package in Raring:
  Invalid
Status in “pixman” source package in Raring:
  Fix Committed

Bug description:
  Bug #1242633 only deals with the packages related to pointer barriers. More packages need to be backported to enable building saucy xserver on precise:
  - Pixman, should be copied to precise, quantal and raring, to not deliberately break dist-upgrading too hard.
  - libdrm, to precise, quantal and raring too, for same reason. Bug #1171340 shows why renaming is unfeasible.

  Mesa in precise needs a small update to recognise -lts-saucy and lts-
  trusty renamed packages.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/libdrm/+bug/1253041/+subscriptions



More information about the foundations-bugs mailing list