Bug 1114123

Summary: RFE: set vstring dynamically
Product: Red Hat Enterprise Linux 7 Reporter: Pat Riehecky <riehecky>
Component: httpdAssignee: Luboš Uhliarik <luhliari>
Status: CLOSED ERRATA QA Contact: Martin Frodl <mfrodl>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 7.0CC: csieh, isenfeld, jkaluza, jorton, mfrodl, misterbonnie
Target Milestone: rcKeywords: FutureFeature
Target Release: ---   
Hardware: All   
OS: Linux   
Whiteboard:
Fixed In Version: httpd-2.4.6-28.el7 Doc Type: Bug Fix
Doc Text:
Cause: While building the httpd, version string has been hard-coded in RPM spec file. Consequence: There was no way how version string could be change automatically during the RPM build. Fix: Version string is now obtained from /etc/os-release file. Result: Version string changes according to the machine when RPM builds.
Story Points: ---
Clone Of:
: 1114539 (view as bug list) Environment:
Last Closed: 2015-03-05 07:12:42 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Bug Depends On:    
Bug Blocks: 1114539    
Attachments:
Description Flags
patch to resolve none

Description Pat Riehecky 2014-06-27 19:41:41 UTC
Created attachment 912941 [details]
patch to resolve

Description of problem: It would be nice if %{vstring} could set itself to the correct value automatically.

The current value is hard coded.


Version-Release number of selected component (if applicable):httpd-2.4.6-17.el7


How reproducible:100%


Steps to Reproduce:
1.open httpd.spec
2.review line beginning with %define vstring
3.

Actual results:
hard coded value

Expected results:
determine the value at build time

Additional info:
The attached patch implements a solution.

Comment 7 errata-xmlrpc 2015-03-05 07:12:42 UTC
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory, and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

https://rhn.redhat.com/errata/RHSA-2015-0325.html