This bug has been migrated to another issue tracking site. It has been closed here and may no longer be being monitored.

If you would like to get updates for this issue, or to participate in it, you may do so at Red Hat Issue Tracker .
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.
Bug 2232517 - The RHEL version of the gcc-toolset-12 metapackage is newer than the CentOS version
Summary: The RHEL version of the gcc-toolset-12 metapackage is newer than the CentOS v...
Keywords:
Status: CLOSED MIGRATED
Alias: None
Product: Red Hat Enterprise Linux 9
Classification: Red Hat
Component: gcc-toolset-12
Version: CentOS Stream
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: rc
: ---
Assignee: Marek Polacek
QA Contact: qe-baseos-tools-bugs
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2023-08-17 08:33 UTC by Nick Clifton
Modified: 2023-09-22 17:58 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: No Doc Update
Doc Text:
Clone Of:
Environment:
Last Closed: 2023-09-22 17:58:31 UTC
Type: Bug
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Issue Tracker   RHEL-7547 0 None Migrated None 2023-09-22 17:58:23 UTC
Red Hat Issue Tracker RHELPLAN-165956 0 None None None 2023-08-17 08:37:43 UTC

Description Nick Clifton 2023-08-17 08:33:11 UTC
Comment 1 Nick Clifton 2023-08-17 08:37:13 UTC 
CentOS has:  gcc-toolset-12-runtime-12.0-5
RHEL has:    gcc-toolset-12-12.0-6

This matters because the -6 release has support for the gcc generated version of the annobin plugin.  cf:

  https://bugzilla.redhat.com/show_bug.cgi?id=2216918#c25
Comment 2 Nick Clifton 2023-08-17 08:38:22 UTC 
Doh - please ignore the "runtime" in the comparison above.  The "runtime" is rpm is just part of the meta package.
Comment 3 Marek Polacek 2023-08-17 12:59:28 UTC 
Confirmed (both rhel 8 and 9) but we don't even have the appropriate branches.

Is this to be fixed in RHEL 9.4/8.10 or 9.3/8.9?
Comment 4 Nick Clifton 2023-08-17 13:20:07 UTC 
(In reply to Marek Polacek from comment #3)
> Confirmed (both rhel 8 and 9) but we don't even have the appropriate
> branches.
> 
> Is this to be fixed in RHEL 9.4/8.10 or 9.3/8.9?

I think both, plus possibly 9.2 and 9.1 and 8.8 as well.

The thing is, this is for GTS-12, which spans multiple releases of RHEL, and needs to work on all of them.  So this probably going to be a y-stream fix for 9.3/8.9 and a z-stream fix for the earlier releases.  Although since we are now so close to exception/blocker time, maybe it will have to be a y-stream fix for 9.4/8.10 and a z-stream for the others.
Comment 5 Marek Polacek 2023-08-17 14:10:55 UTC 
(In reply to Nick Clifton from comment #4)
> (In reply to Marek Polacek from comment #3)
> > Confirmed (both rhel 8 and 9) but we don't even have the appropriate
> > branches.
> > 
> > Is this to be fixed in RHEL 9.4/8.10 or 9.3/8.9?
> 
> I think both, plus possibly 9.2 and 9.1 and 8.8 as well.

I suppose I'm going to have to ask for all these branches to be created...

> The thing is, this is for GTS-12, which spans multiple releases of RHEL, and
> needs to work on all of them.  So this probably going to be a y-stream fix
> for 9.3/8.9 and a z-stream fix for the earlier releases.  Although since we
> are now so close to exception/blocker time, maybe it will have to be a
> y-stream fix for 9.4/8.10 and a z-stream for the others.

...and depending on how fast they are created, the y-stream will be determined.
Comment 6 Marek Polacek 2023-08-17 14:58:14 UTC 
Actually, I don't think we need z-streams for CentOS, just a y-stream branch.
Comment 7 Marek Polacek 2023-08-17 14:59:28 UTC 
Created https://issues.redhat.com/browse/CS-1710
Comment 8 Marek Polacek 2023-08-17 15:44:17 UTC 
But the branches also don't exist in RHEL so I guess I'll need *another* ticket.
Comment 9 Marek Polacek 2023-08-25 16:23:34 UTC 
(In reply to Marek Polacek from comment #8)
> But the branches also don't exist in RHEL so I guess I'll need *another*
> ticket.

https://issues.redhat.com/browse/RHELBLD-13581
Comment 10 RHEL Program Management 2023-09-22 17:56:46 UTC 
Issue migration from Bugzilla to Jira is in process at this time. This will be the last message in Jira copied from the Bugzilla bug.
Comment 11 RHEL Program Management 2023-09-22 17:58:31 UTC 
This BZ has been automatically migrated to the issues.redhat.com Red Hat Issue Tracker. All future work related to this report will be managed there.

Due to differences in account names between systems, some fields were not replicated.  Be sure to add yourself to Jira issue's "Watchers" field to continue receiving updates and add others to the "Need Info From" field to continue requesting information.

To find the migrated issue, look in the "Links" section for a direct link to the new issue location. The issue key will have an icon of 2 footprints next to it, and begin with "RHEL-" followed by an integer.  You can also find this issue by visiting https://issues.redhat.com/issues/?jql= and searching the "Bugzilla Bug" field for this BZ's number, e.g. a search like:

"Bugzilla Bug" = 1234567

In the event you have trouble locating or viewing this issue, you can file an issue by sending mail to rh-issues. You can also visit https://access.redhat.com/articles/7032570 for general account information.
Note You need to log in before you can comment on or make changes to this bug.