Not really understand that why the regression happen in #12 but not in #10.
And I also check installing nvidia-dkms-430 with proposed dkms and it looks 
works well.

installation:
- https://paste.ubuntu.com/p/4wtRyswGvK/

dpkg -l | grep "nvidia\|dkms":
- http://paste.ubuntu.com/p/NMHNr9cWx8/

So, I believe both #10 and #12 is miss alarm.

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

Title:
  priority of OBSOLETE_BY should higher than "force"

Status in OEM Priority Project:
  New
Status in dkms package in Ubuntu:
  Fix Released
Status in dkms source package in Bionic:
  Fix Committed
Status in dkms source package in Disco:
  Fix Committed

Bug description:
  [Impact]
  the priority of OBSOLETE_BY should higher than "force". #89 
https://github.com/dell/dkms/issues/89

  [Test case]
  1. install the dkms package which already patched (also can be found from my 
test ppa[1])
  2. install a DKMS which has OBSOLETE_BY and FORCE
  e.g.ath10k of my testing ppa : [2]
   - the target dkms defined OBSOLETE_BY and FORCE
   - user install dkms on a system which installed kernel version less than 
OBSOLETE_BY and another kernel higher than OBSOLETE_BY
   - the dkms can be installed well.

  [Regression potential]
  medium as it touched the version sanity. This change land a change from 
upstream.

  [1]:https://code.launchpad.net/~alextu/+recipe/2.3-3ubuntu9.5-closes89
  [2]:https://code.launchpad.net/~alextu/+recipe/2.3-3ubuntu9.5-closes89-dkms

To manage notifications about this bug go to:
https://bugs.launchpad.net/oem-priority/+bug/1838921/+subscriptions

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

Reply via email to