Bug 249735

Summary:	Berkeley db4 4.6.18 is released
Product:	[Fedora] Fedora	Reporter:	Robert Scheck <redhat-bugzilla>
Component:	db4	Assignee:	Jindrich Novy <jnovy>
Status:	CLOSED RAWHIDE	QA Contact:	Fedora Extras Quality Assurance <extras-qa>
Severity:	low	Docs Contact:
Priority:	low
Version:	rawhide	CC:	pknirsch
Target Milestone:	---
Target Release:	---
Hardware:	All
OS:	Linux
URL:	http://www.oracle.com/technology/documentation/berkeley-db/db/ref/changelog/4.6.html
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2007-08-17 07:19:13 UTC	Type:	---
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:
Bug Depends On:
Bug Blocks:	249737, 249740, 249741

Description Robert Scheck 2007-07-26 18:44:34 UTC

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):
db4-4.5.20-5

Actual results:
db4-4.5.20-5

Expected results:
db4-4.6.18-1 or newer ;-)

Comment 1 Jindrich Novy 2007-07-31 09:54:57 UTC

*** Bug 250234 has been marked as a duplicate of this bug. ***

Comment 2 Jindrich Novy 2007-07-31 09:57:36 UTC

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.