Hide Forgot
NOTE: The bug is related to "Red Hat Enterprise Linux Server release 7.0 Alpha3" but it wasn't in the products list, so i put under RHEL6. ###### Description of problem: While creating a kernel module package using kernel_module_package. The %{kernel_source $flavor} expands to a non-existing directory: -------------------------------------------- make: *** /usr/src/kernels/3.7.0-0.36.el7-x86_64: No such file or directory. Stop. make: *** [kernel] Error 2 error: Bad exit status from /var/tmp/rpm-tmp.fl4iBx (%build) -------------------------------------------- %{kernel_source $flavor} returned a path that doesn’t exist: /usr/src/kernels/3.7.0-0.36.el7-x86_64 it should return: /usr/src/kernels/3.7.0-0.36.el7.x86_64 with a dot "." instead of a hyphen before the architecture. Also, rpm --eval %{kernel_module_package} gives: %defattr(644,root,root,755) /lib/modules/3.7.0-0.36.el7/ /lib/firmware/ 1. The architecture is missing in path "/lib/modules/3.7.0-0.36.el7/". it should be "/lib/modules/3.7.0-0.36.el7.x86_64/". 2. "/lib/firmware/" is not always needed by all packages, so i don't think that it should be here. ##### Version-Release number of selected component (if applicable): redhat-rpm-config-9.1.0-37.el7.noarch ##### How reproducible: always ##### Steps to Reproduce: 1. Create a spec file using kernel_module_package (and kernel_source). 2. Build. 3. It will fail because of the missing directory. ##### Actual results: %{kernel_source $flavor} returns: /usr/src/kernels/3.7.0-0.36.el7-x86_64 ##### Expected results: %{kernel_source $flavor} should return: /usr/src/kernels/3.7.0-0.36.el7.x86_64 (with a dot "." instead of a hyphen before the architecture.)
The fix for this bug is already included in the patch for bug 928599, and that bug is fixed in 9.1.0-49 for redhat-rpm-config.
the issue was resolved with version 9.1.0-49. thanks.
Accordering to the bug description, the product of this bug should be "Red Hat Enterprise Linux 7", so I will modify it. And accordering to commet 3, this bug is fixed, so I will close it with a dupliacate of bug 928599.
*** This bug has been marked as a duplicate of bug 928599 ***