Note: This bug is displayed in read-only format because
the product is no longer active in Red Hat Bugzilla.
RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
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.
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.
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
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.