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.
The "package-cleanup" script no longer removes package dependencies of non-duplicates
Previously, running the "package-cleanup" script with the "--cleandupes" option also removed packages that depended on duplicates. Consequently, some packages were removed unintentionally. With this update, the "package-cleanup" script has been fixed to skip package dependencies of non-duplicates. Instead, the "package-cleanup" script prints a warning with a suggestion of a workaround.
Description of problem:
# package-cleanup --cleandupes
This command will remove the lower version for each pair of duplicates that it finds. When it removes the lower version, it can also remove dependencies of those packages. That happens when the dependency isn't a duplicate.
Version-Release number of selected component (if applicable):
package-cleanup
yum-utils
How reproducible:
Everytime a duplicate package is a requirement of a non-duplicate package.
Steps to Reproduce:
####This is just an example with NetworkManager.
####It can happen with any packages that depend on each other.
1. # rpm -qa NetworkManager-libnm
NetworkManager-libnm-1.0.0-14.git20150121.b4ea599c.el7.x86_64
2. # rpm -ivh --force --justdb NetworkManager-libnm-1.4.0-19.el7_3.x86_64.rpm
3. # package-cleanup --dupes
Loaded plugins: langpacks, product-id
NetworkManager-libnm-1.4.0-19.el7_3.x86_64
NetworkManager-libnm-1.0.0-14.git20150121.b4ea599c.el7.x86_64
4. # package-cleanup --cleandupes
Actual results:
Removing:
NetworkManager-libnm x86_64 1:1.0.0-14.git20150121.b4ea599c.el7 @anaconda/7.1 1.4 M
Removing for dependencies:
NetworkManager x86_64 1:1.0.0-14.git20150121.b4ea599c.el7 @anaconda/7.1 8.8 M
NetworkManager-team x86_64 1:1.0.0-14.git20150121.b4ea599c.el7 @anaconda/7.1 32 k
NetworkManager-tui x86_64 1:1.0.0-14.git20150121.b4ea599c.el7 @anaconda/7.1 258 k
Expected results:
package-cleanup verifies if it should remove the lower or the higher version duplicate. Potentially it would judge which version would cause the least amount of damage to the system. Verifying the files against both duplicates to see which package is actually installed.
Or if it could have a flag to affect only the rpm database, or ignore package dependencies.
Additional info:
cleandupes has no warnings to customers. Especially customers who have duplicates and GNOME installed, the issue becomes much much worst and removes majority of the system.
The only thing that forces it to stop, is if it tries to remove yum.
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, 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-2018:0919
Description of problem: # package-cleanup --cleandupes This command will remove the lower version for each pair of duplicates that it finds. When it removes the lower version, it can also remove dependencies of those packages. That happens when the dependency isn't a duplicate. Version-Release number of selected component (if applicable): package-cleanup yum-utils How reproducible: Everytime a duplicate package is a requirement of a non-duplicate package. Steps to Reproduce: ####This is just an example with NetworkManager. ####It can happen with any packages that depend on each other. 1. # rpm -qa NetworkManager-libnm NetworkManager-libnm-1.0.0-14.git20150121.b4ea599c.el7.x86_64 2. # rpm -ivh --force --justdb NetworkManager-libnm-1.4.0-19.el7_3.x86_64.rpm 3. # package-cleanup --dupes Loaded plugins: langpacks, product-id NetworkManager-libnm-1.4.0-19.el7_3.x86_64 NetworkManager-libnm-1.0.0-14.git20150121.b4ea599c.el7.x86_64 4. # package-cleanup --cleandupes Actual results: Removing: NetworkManager-libnm x86_64 1:1.0.0-14.git20150121.b4ea599c.el7 @anaconda/7.1 1.4 M Removing for dependencies: NetworkManager x86_64 1:1.0.0-14.git20150121.b4ea599c.el7 @anaconda/7.1 8.8 M NetworkManager-team x86_64 1:1.0.0-14.git20150121.b4ea599c.el7 @anaconda/7.1 32 k NetworkManager-tui x86_64 1:1.0.0-14.git20150121.b4ea599c.el7 @anaconda/7.1 258 k Expected results: package-cleanup verifies if it should remove the lower or the higher version duplicate. Potentially it would judge which version would cause the least amount of damage to the system. Verifying the files against both duplicates to see which package is actually installed. Or if it could have a flag to affect only the rpm database, or ignore package dependencies. Additional info: cleandupes has no warnings to customers. Especially customers who have duplicates and GNOME installed, the issue becomes much much worst and removes majority of the system. The only thing that forces it to stop, is if it tries to remove yum.