Bug 1965640

Summary:	inconsistent Release version String and gcc/DEV-PHASE string
Product:	Red Hat Enterprise Linux 8	Reporter:	Qing Zhao <Qing.zhao>
Component:	gcc	Assignee:	Marek Polacek <mpolacek>
gcc sub component:	system-version	QA Contact:	qe-baseos-tools-bugs
Status:	CLOSED NOTABUG	Docs Contact:
Severity:	medium
Priority:	unspecified	CC:	ahajkova, fweimer, jakub, jose.marchesi, ohudlick
Version:	8.3	Keywords:	Triaged
Target Milestone:	beta
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2021-06-01 18:32:32 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:

Description Qing Zhao 2021-05-28 16:54:46 UTC

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:

Comment 1 Marek Polacek 2021-06-01 17:59:18 UTC

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?

Comment 2 Jakub Jelinek 2021-06-01 18:14:13 UTC

It is intentional, from the DEV-PHASE macros then gcc computes __GCC_RH_RELEASE__.