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:
Version-Release number of selected component (if applicable):
How reproducible:
Steps to Reproduce:
1. enable optional repository
2. yum install xchat
3. leapp upgrade
Actual results:
Running transaction check
Error: transaction check vs depsolve:
(enchant or enchant2) is needed by hexchat-2.14.1-2.el8.x86_64
rpmlib(RichDependencies) <= 4.12.0-1 is needed by hexchat-2.14.1-2.el8.x86_64
To diagnose the problem, try running: 'rpm -Va --nofiles --nodigest'.
You probably have corrupted RPMDB, running 'rpm --rebuilddb' might fix the issue.
The downloaded packages were saved in cache until the next successful transaction.
You can remove cached packages by executing 'dnf clean packages'.
Expected results:
Running transaction check
Transaction check succeeded.
Running transaction test
Transaction test succeeded.
Running transaction
Preparing : 1/1
Complete!
The downloaded packages were saved in cache until the next successful transaction.
You can remove cached packages by executing 'dnf clean packages'.
Additional info:
Workaround is to remove xchat from system, the try again to upgrade.
# yum remove xchat
===================================================================================================================================================================================
Package Arch Version Repository Size
===================================================================================================================================================================================
Removing:
xchat x86_64 1:2.8.8-23.el7 @rhel-7-server-optional-rpms 3.7 M
Transaction Summary
===================================================================================================================================================================================
Remove 1 Package
Comment 2Vinzenz Feenstra [evilissimo]
2019-06-14 08:26:04 UTC
This is a known problem - Currently packages that would required rich dependencies are not supported and need to be removed. Another way beside removing it manually is adding xchat to /etc/leapp/transaction/to_remove
However the linked GitHub Pull Request is already adding support for newer RPM features and in a future release will be taken care of.
Jay, could you please rerun your use case with the latest publicly released leapp-repository? Packages with rich dependencies shouldn't be causing failures during the upgrade now.