Bug 139416 - poor packaging of libdb-4.3 and libdb-4.2
poor packaging of libdb-4.3 and libdb-4.2
Product: Fedora
Classification: Fedora
Component: db4 (Show other bugs)
i386 Linux
medium Severity low
: ---
: ---
Assigned To: Jeff Johnson
Depends On:
  Show dependency treegraph
Reported: 2004-11-15 16:36 EST by Sean Middleditch
Modified: 2007-11-30 17:10 EST (History)
0 users

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2004-11-15 16:56:30 EST
Type: ---
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 Sean Middleditch 2004-11-15 16:36:21 EST
From Bugzilla Helper:
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.7.3)
Gecko/20041020 Epiphany/1.4.4

Description of problem:
The db4 package is poorly versioned.  Version 4.2 is fully
co-installable with version 4.3, and back to older versions as well.

Instead of having the silly compat-db4 package (which is then only
compat with a single version), the package should just be broken up
into db4.2, db4.3, and so on.  There would be no problems with
upgrading, older versions can *easily* be kept in the tree, and the
entire process of dealing with the db4 situation becomes a piece of cake.

Version-Release number of selected component (if applicable):
db4-4.3.21-1 db4-4.2.52-6

How reproducible:

Steps to Reproduce:
1. upgrade one component that needs db4-4.3 while another one still
need db4-4.2 and yet another needs db4-4.1

Additional info:
Comment 1 Jeff Johnson 2004-11-15 16:56:30 EST
There is no known interest in supporting multiple versions of libdb
concurrently in FC4. Nor is there any compelling reason to do so.

All FC4 packages that use the system provided db should be linked with
db-4.3.21. If not, then that is a bug that will be identified and fixed

The compat-db package carries the previous libary (and soname) to make
the transition easier.

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