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.
Description of problem:
The Release version string is inconsistent with the gcc/DEV-PHASE string.
Version-Release number of selected component (if applicable):
How reproducible:
In gcc.spec file, we have:
%global gcc_release 5
Release: %{gcc_release}.1%{?dist}
echo 'Red Hat %{version}-%{gcc_release}' > gcc/DEV-PHASE
from the above, we can see, the string that is echoed to gcc/DEV-PHASE missed the suffix ".1" after %{gcc_release}, is this intended or is a bug?
if it's intended, what the reason not echoing the suffix ".1" into gcc/DEV-PHASE.
all the redhat gcc releases have the same behavior.
Additional info:
This behavior is inherited from Fedora gcc. I don't think it's a bug though: %{version} and %{gcc_release} is what really matters, adding .N to Release is usually used for trivial rebuilds and minor changes, but not for updates from upstream.
What problems does this cause?
Description of problem: The Release version string is inconsistent with the gcc/DEV-PHASE string. Version-Release number of selected component (if applicable): How reproducible: In gcc.spec file, we have: %global gcc_release 5 Release: %{gcc_release}.1%{?dist} echo 'Red Hat %{version}-%{gcc_release}' > gcc/DEV-PHASE from the above, we can see, the string that is echoed to gcc/DEV-PHASE missed the suffix ".1" after %{gcc_release}, is this intended or is a bug? if it's intended, what the reason not echoing the suffix ".1" into gcc/DEV-PHASE. all the redhat gcc releases have the same behavior. Additional info: