Red Hat Bugzilla – Bug 643272
unresolved deps in kmod-kvm-debug-83-205.el5
Last modified: 2013-01-09 18:14:23 EST
package: kmod-kvm-debug-83-205.el5.x86_64 from file:///mnt/redhat/devel/candidate-trees/RHEL5.6-Client-20101014.0/5/x86_64/os/Client unresolved deps: kernel(lib) = 0:60733029a5eba6716566a4cb827d9bb623b8b731 kernel(kernel) = 0:027aed1cf4fd2611dfcb523abfe5f51e1012b7ea kernel(arch_x86_64_kernel) = 0:62afda903797355ca79e123bdfb6ff6f485a7f77 kernel(drivers) = 0:a551bed789de2a5f8d1f7ff1013c0db6ca6ffdc0 kernel(fs) = 0:e0359c8348ae55143920c44516857b48b82c13bc kernel(drivers_base) = 0:45a4d31daa2182ca84b7fe592edf486390c04a6d The same problem appears on Server.
All the symbols mentioned on comment #0 are provided by kernel-debug-2.6.18-226.el5, but not by 2.6.18-227.el5. Does this mean that it is impossible to make a kmod for kernel-debug that works across kernel versions (like the kmods for non-debug kernels)? Adding Jon Masters to CC. For reference: the kmods for kernel-debug were added for bug #517565.
Yea, we don't support ABI on debug kernels sorry.
(In reply to comment #4) > Yea, we don't support ABI on debug kernels sorry. I just noticed that the module can be loaded against a newer kernel. Do the 'kernel(*)' provides from kernel-debug mean anything? I could simply ignore the automatic requires on kmod-kvm-debug, and expect the user to install a compatible kernel. Not a perfect solution, but it is better than not providing any module for kernel-debug. Jon, what do you think?
Basically, those provides are there, but there's no guarantee backing them not changing. You could just turn off the deps for the debug kernel and tell the user they must have the right kernel (which you can describe), etc. Since it's only the debug kernel and only intended for specific testing, probably ok for now. We should come up with a better solution if this is needed elsewhere, but the whole thing is different in RHEL6 anyway.
according to comment 11,set this issue status as verified.
great
An advisory has been issued which should help the problem described in this bug report. This report is therefore being closed with a resolution of ERRATA. For more information on therefore solution and/or where to find the updated files, please follow the link below. You may reopen this bug report if the solution does not work for you. http://rhn.redhat.com/errata/RHSA-2011-0028.html