Bug 1104578

Summary: vhba-kmp-default still requires outdated kernel (update needed)
Product: [openSUSE] openSUSE Distribution Reporter: kolA flash <kolAflash>
Component: OtherAssignee: E-mail List <kernel-maintainers>
Status: RESOLVED DUPLICATE QA Contact: E-mail List <qa-bugs>
Severity: Normal    
Priority: P5 - None CC: astieger, jengelh, tiwai
Version: Leap 15.0   
Target Milestone: ---   
Hardware: x86-64   
OS: Other   
Whiteboard:
Found By: --- Services Priority:
Business Priority: Blocker: ---
Marketing QA Status: --- IT Deployment: ---

Description kolA flash 2018-08-11 10:35:50 UTC
vhba-kmp-default still depends on the outdated openSUSE 15.0 kernel kernel-default-4.12.14-lp150.11.4.x86_64.


When uninstalling kernel-default-4.12.14-lp150.11.4.x86_64, zypper says this.
(deny the installation of kernel-default-base and keep vhba-kmp-default installed)

zypper> al vhba-kmp-default kernel-default-base
Specified locks have been successfully added.
zypper> remove kernel-default-4.12.14-lp150.11.4
Resolving package dependencies...

Problem: vhba-kmp-default-20170610_k4.12.14_lp150.11-lp150.1.36.x86_64 requires kernel-uname-r = 4.12.14-lp150.11-default, but this requirement cannot be provided
  deleted providers: kernel-default-4.12.14-lp150.11.4.x86_64
 Solution 1: remove lock to allow removal of vhba-kmp-default-20170610_k4.12.14_lp150.11-lp150.1.36.x86_64
 Solution 2: keep kernel-default-4.12.14-lp150.11.4.x86_64
 Solution 3: break vhba-kmp-default-20170610_k4.12.14_lp150.11-lp150.1.36.x86_64 by ignoring some of its dependencies

Choose from above solutions by number or cancel [1/2/3/c] (c):
Comment 1 Jan Engelhardt 2018-08-11 14:02:21 UTC
Seems to be an issue with all KMPs (including bbswitch).
Comment 2 Takashi Iwai 2018-08-11 15:12:51 UTC
This is a dup of bug 1095148.
Basically all affected KMPs have to be rebuilt with the fixed rpm package...
Comment 3 Andreas Stieger 2018-08-11 19:19:19 UTC
in https://build.opensuse.org/project/show/openSUSE:Maintenance:8582

*** This bug has been marked as a duplicate of bug 1095148 ***