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.
Sanity check for the below packages, all have been rebased.
mingw-gcc-12.2.1-4.el9
mingw-binutils-2.39-2.el9
mingw-crt-10.0.0-3.el9
mingw-headers-10.0.0-4.el9
mingw-w64-tools-10.0.0-2.el9
For mingw-filesystem,the latest package in brewweb is mingw-filesystem-139-1.el9 which is built during RHEL9.1.
For mingw-winpthreads, the latest package in brewweb is mingw-winpthreads-10.0.0-2.el9 which is built during RHEL9.1.
Do we need to rebase mingw-filesystem and mingw-winpthreads for RHEL9.2?
Comment 6Richard W.M. Jones
2023-01-05 10:41:07 UTC
(In reply to Richard W.M. Jones from comment #6)
> I synchronized them with Fedora, but there was no version-release
> change and no significant changes to the packages, so I didn't need
> to rebuild them.
Got it, thanks.
Another question is we use only one bug(component mingw-gcc) to track 5 mingw-* packages, then only 1 errata will be created. If there are no more bugs filed against other mings-* components, then these packages will not be added in latest RHEL9.2 nightly compose. As far as I know, when pre-verification testing is finished and bug is added in errata, then the package will be added in latest nightly compose.
Comment 8Richard W.M. Jones
2023-01-05 12:57:32 UTC
This is annoying ...
Comment 9Richard W.M. Jones
2023-01-05 14:05:03 UTC
Test the bug with:
mingw-gcc-12.2.1-4.el9
Tried to install mingw-gcc-12.2.1-4 packages and they can be installed successfully, so set Verified:Tested/Sanity only.
Tested with:
mingw-gcc-12.2.1-4.el9
The package can be installed successfully and it's included in latest nightly compose, so move the bug to VERIFIED.
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.
For information on the advisory (mingw-gcc bug fix and enhancement update), and where to find the updated
files, follow the link below.
If the solution does not work for you, open a new bug report.
https://access.redhat.com/errata/RHBA-2023:2595