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:

The new debuginfo experience is deeply unpleasant and irritating.

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


How reproducible:


Steps to Reproduce:
1. Experience a software crash, type "yum install [package]-debuginfo"
2. Receive message "No package [package]-debuginfo available"
3. **** around for an hour or two reading conflicting reports of weird new settings to enable separate repos that are disabled for no good reason, and to run weird new commands that exist for no good reason, and that are inconsistent across distros and versions.

Actual results:

Huge amounts of wasted time and unnecessary googling to fix something that wasn't broken to start with.

Expected results:

debuginfo package installs first time without any screwing around.

Additional info:

To fix this bug, force the dev responsible for it to endure "No package [package]-debuginfo available" over and over again until they have learned their lesson not to do something so stupid again.

The 'yum-utils' package contains the 'debuginfo-install' utility which can help with this.