Bug 249735 - Berkeley db4 4.6.18 is released
Berkeley db4 4.6.18 is released
Product: Fedora
Classification: Fedora
Component: db4 (Show other bugs)
All Linux
low Severity low
: ---
: ---
Assigned To: Jindrich Novy
Fedora Extras Quality Assurance
: 250234 (view as bug list)
Depends On:
Blocks: 249737 249740 249741
  Show dependency treegraph
Reported: 2007-07-26 14:44 EDT by Robert Scheck
Modified: 2013-07-02 19:22 EDT (History)
1 user (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2007-08-17 03:19:13 EDT
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 Robert Scheck 2007-07-26 14:44:34 EDT
Description of problem:
Berkeley db4 4.6.18 (stable) was released some time ago and Fedora development 
hangs around the older 4.5.20...

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

Actual results:

Expected results:
db4-4.6.18-1 or newer ;-)
Comment 1 Jindrich Novy 2007-07-31 05:54:57 EDT
*** Bug 250234 has been marked as a duplicate of this bug. ***
Comment 2 Jindrich Novy 2007-07-31 05:57:36 EDT
I updated db4 to 4.6.18 and moved the 4.5.20 to compat-db in CVS for now.

I need to catch up with rel-eng whether it won't break anything and then I build
it after PAM with increased conflict to db4 is built.

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