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.
Summary of the issue
DNF is still unable to process too large changelogs, but the issue was resolved by a change in the RHEL infrastructure. The current available RHEL metadata has reasonable size of changelogs. It means that issue cannot be reproduce in RHEl anymore.
According to libsolv upstream (dnf solver that reads changelogs), support of too large change logs will be very difficult and sooner or later we will end up with additional limit. Additionally infrastructure had a difficulty to generate such a metadata due to resource requirement. Because the issue has workaround using alternative way how to generate metadata, there is a low chance to have such a patch in near future.
I am closing the bug but I have difficulty with a reason - I could use - current release, because the issue was already resolved by metadata update (comment 27), or cantfix because we have no solution to support of large changelogs. But CURRENTRELEASE should create less questions about the state in RHEL distribution.