Bug 814082

Summary:	Move from db4 to db5
Product:	[Fedora] Fedora	Reporter:	Petr Pisar <ppisar>
Component:	perl-eperl	Assignee:	Steven Pritchard <steve>
Status:	CLOSED CURRENTRELEASE	QA Contact:	Fedora Extras Quality Assurance <extras-qa>
Severity:	unspecified	Docs Contact:
Priority:	unspecified
Version:	19	CC:	perl-devel, steve
Target Milestone:	---
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:	perl-eperl-2.2.14-22.fc18	Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2014-01-28 11:28:02 UTC	Type:	Bug
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:

Description Petr Pisar 2012-04-19 08:06:18 UTC

Because of bug #768846, I'd like to see all Perl packages being linked against
the same Berkeley database library version.

Currently latest perl-eperl-2.2.14-19.fc17 links to db4. Please replace `db4-devel' build-require with `libdb-devel'. According my tests, all compilation and tests will pass.

Comment 1 Fedora End Of Life 2013-04-03 17:42:02 UTC

This bug appears to have been reported against 'rawhide' during the Fedora 19 development cycle.
Changing version to '19'.

(As we did not run this process for some time, it could affect also pre-Fedora 19 development
cycle bugs. We are very sorry. It will help us with cleanup during Fedora 19 End Of Life. Thank you.)

More information and reason for this action is here:
https://fedoraproject.org/wiki/BugZappers/HouseKeeping/Fedora19