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.
DescriptionAndrei Stepanov
2019-05-07 14:45:28 UTC
dnf update --allowerasing just removes package
Here are commands I run:
[root@rhel8-7737 bin]# rpm -q python3-ldb-devel
python3-ldb-devel-1.4.2-2.el8.x86_64
[root@rhel8-7737 bin]# dnf list --showduplicates python3-ldb-devel
Last metadata expiration check: 0:14:21 ago on Tue 07 May 2019 10:21:28 AM EDT.
Installed Packages
python3-ldb-devel.x86_64 1.4.2-2.el8 @rhel-8-buildroot
Available Packages
python3-ldb-devel.x86_64 1.4.2-2.el8 @rhel-8-buildroot
python3-ldb-devel.x86_64 1.4.2-2.el8 rhel-8-buildroot
python3-ldb-devel.x86_64 1.5.4-1.el8 brew-21544647
[root@rhel8-7737 bin]# dnf update --allowerasing python3-ldb-devel
Last metadata expiration check: 0:14:43 ago on Tue 07 May 2019 10:21:28 AM EDT.
Dependencies resolved.
================================================================================
Package Arch Version Repository Size
================================================================================
Removing:
python3-ldb-devel x86_64 1.4.2-2.el8 @rhel-8-buildroot 354
Transaction Summary
================================================================================
Remove 1 Package
Freed space: 354
Is this ok [y/N]: y
Running transaction check
Transaction check succeeded.
Running transaction test
Transaction test succeeded.
Running transaction
Preparing : 1/1
Erasing : python3-ldb-devel-1.4.2-2.el8.x86_64 1/1
Running scriptlet: python3-ldb-devel-1.4.2-2.el8.x86_64 1/1
Verifying : python3-ldb-devel-1.4.2-2.el8.x86_64 1/1
Removed:
python3-ldb-devel-1.4.2-2.el8.x86_64
Complete!
[root@rhel8-7737 bin]# rpm -q python3-ldb-devel
package python3-ldb-devel is not installed
I asked DNF to update the package. DNF just removed the current, without updating to the newest.
[root@rhel8-7737 bin]# dnf install python3-ldb-devel-1.5.4-1.el8.x86_64
Last metadata expiration check: 0:17:59 ago on Tue 07 May 2019 10:21:28 AM EDT.
Error:
Problem: problem with installed package python-ldb-devel-common-1.4.2-2.el8.x86_64
- package python3-ldb-devel-1.5.4-1.el8.x86_64 conflicts with python-ldb-devel-common(x86-64) < 1.5.4-1.el8 provided by python-ldb-devel-common-1.4.2-2.el8.x86_64
- conflicting requests
(try to add '--allowerasing' to command line to replace conflicting packages or '--skip-broken' to skip uninstallable packages or '--nobest' to use not only best candidate packages)
Anyway, DNF should not just remove package for `dnf update` command.
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/RHSA-2019:3583