Bug 1474735 - Issue on rpm macro "latest_kernel"
Issue on rpm macro "latest_kernel"
Status: NEW
Product: Fedora
Classification: Fedora
Component: redhat-rpm-config (Show other bugs)
27
All Unspecified
unspecified Severity medium
: ---
: ---
Assigned To: Florian Festi
Fedora Extras Quality Assurance
:
Depends On:
Blocks:
  Show dependency treegraph
 
Reported: 2017-07-25 05:45 EDT by Ronan
Modified: 2017-08-15 03:40 EDT (History)
5 users (show)

See Also:
Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed:
Type: Bug
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


Attachments (Terms of Use)
Fix on https://src.fedoraproject.org/git/rpms/redhat-rpm-config.git (1.24 KB, application/mbox)
2017-07-25 05:45 EDT, Ronan
no flags Details

  None (edit)
Description Ronan 2017-07-25 05:45:17 EDT
Created attachment 1304142 [details]
Fix on https://src.fedoraproject.org/git/rpms/redhat-rpm-config.git

Description of problem:
If you use The macro :
%kernel_module_package

In a spec file, the value is the value of the package, not the kernel.

Version-Release number of selected component (if applicable):


How reproducible:

Steps to Reproduce:
1. Include %kernel_module_package in a spec file
2. use macro %latest_kernel
3. echo %latest_kernel

Actual results:
return the version/release of the current package

Expected results:

return the version/release of the last kernel

Additional info:
Comment 1 Jan Kurik 2017-08-15 03:40:18 EDT
This bug appears to have been reported against 'rawhide' during the Fedora 27 development cycle.
Changing version to '27'.

Note You need to log in before you can comment on or make changes to this bug.