Bug 823027 - rpm prevents installation of db 5.x utilities
rpm prevents installation of db 5.x utilities
Product: Fedora
Classification: Fedora
Component: rpm (Show other bugs)
All Linux
unspecified Severity low
: ---
: ---
Assigned To: Fedora Packaging Toolset Team
Fedora Extras Quality Assurance
Depends On:
  Show dependency treegraph
Reported: 2012-05-18 16:08 EDT by Jeff Garzik
Modified: 2013-07-02 22:40 EDT (History)
6 users (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2013-02-13 15:51:41 EST
Type: Bug
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)

  None (edit)
Description Jeff Garzik 2012-05-18 16:08:00 EDT
Description of problem:
The "rpm" package requires "db4-utils" pkg.  db4-utils conflicts with libdb-utils.

Thus, rpm -- required for all Fedora installations -- prevents installation and use of db 5.x utilities.

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

How reproducible:

Steps to Reproduce:
1. Install Fedora.
2. Attempt to remove db4-utils, or, install libdb-utils.
Actual results:
[jgarzik@bd data]$ sudo rpm -e db4-utils
error: Failed dependencies:
	db4-utils is needed by (installed) rpm-

Expected results:
Able to install and use libdb-utils.

Additional info:
Comment 1 Panu Matilainen 2012-05-23 10:29:26 EDT
Yes, well known. Rpm requires what it requires for a reason, the fundamental issue is the lack of proper transition from db4 -> libdb during the rawhide cycle that introduced libdb.

For rpm at least, this has been fixed in F >= 17 but there's no good way to address it in the already released versions: there are several packages (including rpm) depending on db4-utils that would break if the /usr/bin/db_foo utilities just changed to libdb versions. Technically resolvable by rebuilding all the packages against libdb and releasing a big update covering all the related packages, fo but changing the underlying BDB version is not necessarily (depends a bit on how the software uses BDB) that can be sanely/safely done in an errata-update. Rpm could switch to internal copy of the current BDB 4.x version that would help a bit, but doesn't resolve the entire issue.
Comment 2 Jeff Garzik 2012-05-23 12:06:27 EDT
As rpm and these other utilities now require a not-current version of db utils, what about renaming all those utils to db48_stat, db48_recover, db48_tuner, etc.?

This was done in the past, IIRC, and it does usefully indicate that $PACKAGE requires a specific version of utils, and cannot make do with the current version.
Comment 3 Panu Matilainen 2012-05-24 02:07:56 EDT
Sure... but again that's something that should've been done in rawhide when libdb was introduced, changing "common" utility names in a released distro is rude. Fedora might not have all that many bits and pieces relying on those utilities but who knows about 3rd party repositories and other software.
Comment 4 Fedora End Of Life 2013-01-16 11:49:29 EST
This message is a reminder that Fedora 16 is nearing its end of life.
Approximately 4 (four) weeks from now Fedora will stop maintaining
and issuing updates for Fedora 16. It is Fedora's policy to close all
bug reports from releases that are no longer maintained. At that time
this bug will be closed as WONTFIX if it remains open with a Fedora 
'version' of '16'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version' 
to a later Fedora version prior to Fedora 16's end of life.

Bug Reporter: Thank you for reporting this issue and we are sorry that 
we may not be able to fix it before Fedora 16 is end of life. If you 
would still like to see this bug fixed and are able to reproduce it 
against a later version of Fedora, you are encouraged to click on 
"Clone This Bug" and open it against that version of Fedora.

Although we aim to fix as many bugs as possible during every release's 
lifetime, sometimes those efforts are overtaken by events. Often a 
more recent Fedora release includes newer upstream software that fixes 
bugs or makes them obsolete.

The process we are following is described here: 
Comment 5 Fedora End Of Life 2013-02-13 15:51:49 EST
Fedora 16 changed to end-of-life (EOL) status on 2013-02-12. Fedora 16 is 
no longer maintained, which means that it will not receive any further 
security or bug fix updates. As a result we are closing this bug.

If you can reproduce this bug against a currently maintained version of 
Fedora please feel free to reopen this bug against that version.

Thank you for reporting this bug and we are sorry it could not be fixed.

Note You need to log in before you can comment on or make changes to this bug.