Bug 1965640 - inconsistent Release version String and gcc/DEV-PHASE string
Summary: inconsistent Release version String and gcc/DEV-PHASE string
Keywords:
Status: CLOSED NOTABUG
Alias: None
Product: Red Hat Enterprise Linux 8
Classification: Red Hat
Component: gcc
Version: 8.3
Hardware: Unspecified
OS: Unspecified
unspecified
medium
Target Milestone: beta
: ---
Assignee: Marek Polacek
QA Contact: qe-baseos-tools-bugs
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2021-05-28 16:54 UTC by Qing Zhao
Modified: 2023-07-18 14:19 UTC (History)
5 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2021-06-01 18:32:32 UTC
Type: Bug
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)

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__.


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