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:
We need to bump the release of the mecab package in the mysql module (mecab-0.996-1.module).
The problem is that there was a change in the package suffix from *.el8 to *.el8.0.0, however, RPM thinks that the *.el8 is a newer package than the *.el8.0.0, which is not true.
This leads to the failed TPS tests, which just adds work for the QA folks.
The description of the problem is here: https://errata.devel.redhat.com/advisory/80632#c21
During this rebuild, we will need to rebuild the whole mysql module.
We agreed to fix this after the current errata to ease from the backlog of QA folks and ours as well.
This will be fixed with a simple release bump and rebuild (it should be possible to build just a mecab package, same as we do with mysql)