dropped libclc, yakkety shipped with the same version

** Changed in: libclc (Ubuntu Xenial)
       Status: Incomplete => Won't Fix

** Also affects: mesa (Ubuntu)
   Importance: Undecided
       Status: New

** Changed in: mesa (Ubuntu)
       Status: New => Invalid

** Description changed:

  [Impact]
  We need a few packages backported to xenial for lts-hwe X stack.
  
  [Test case]
  
- libdrm: run a desktop session, see that things still work
- libclc: TBD
+ libdrm, mesa: run a desktop session, see that things still work
  
  [Regression potential]
  
  slim to none, changes from 2.4.67..2.4.70:
  - amdgpu: spelling fixes
  - ati: typo-/make check fixes
  - intel: pci-id changes, already SRU'd
  - nouveau: only some android makefile diff
  - core: drmGetDevice fixes for multi-gpu

** Description changed:

  [Impact]
  We need a few packages backported to xenial for lts-hwe X stack.
  
  [Test case]
  
  libdrm, mesa: run a desktop session, see that things still work
  
  [Regression potential]
  
+ libdrm:
  slim to none, changes from 2.4.67..2.4.70:
  - amdgpu: spelling fixes
  - ati: typo-/make check fixes
  - intel: pci-id changes, already SRU'd
  - nouveau: only some android makefile diff
  - core: drmGetDevice fixes for multi-gpu
+ 
+ mesa:
+ slim
+ - Intel validates new upstream releases on all their hw
+ - AMD probably does the same, though it's unverified
+ - was already tested by cert team on a handful of intel/amd machines

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

Title:
  Backport packages for 16.04.2 lts-hwe stack

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

_______________________________________________
Mailing list: https://launchpad.net/~ubuntu-x-swat
Post to     : ubuntu-x-swat@lists.launchpad.net
Unsubscribe : https://launchpad.net/~ubuntu-x-swat
More help   : https://help.launchpad.net/ListHelp

Reply via email to