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:

Lots and lots of OSCI errors like this:

https://dashboard.osci.redhat.com/#/artifact/brew-build/aid/45136815?focus=id:58479ba5ee2d5280b1f2cc5eb3b67144f712ae8f7854568ee027b6ba094b63fa

  Problems with dependency set:
  nothing provides mingw32-libgcc needed by mingw32-gcc-12.0.1-11.1.el9.x86_64
  nothing provides mingw64-libgcc needed by mingw64-gcc-12.0.1-11.1.el9.x86_64

These are new packages (previously the files were included in the
base mingw*-gcc package).  The new packages need to be added to
the compose in order for these tests to pass, which probably means
adding them to comps?

However the new mingw*-gcc has a Requires on mingw*-libgcc, so
perhaps we don't need to do anything here?

Version-Release number of selected component (if applicable):

mingw64-gcc-12.0.1-11.1.el9

Josh, could you advise on what we need to do here?

(In reply to Richard W.M. Jones from comment #1)
> Josh, could you advise on what we need to do here?

If there's a runtime requires from mingw*-gcc, it should automatically pull mingw*-libgcc into the compose without changes after the build is attached to an errata.  Should be in tomorrow's compose if everything lines up.  If not, we'll figure out why.

Yes these are now in the compose.