Bug 156070

Summary:	conflict with DB_CONFIG
Product:	[Fedora] Fedora	Reporter:	David Relson <relson>
Component:	rpm	Assignee:	Paul Nasrat <nobody+pnasrat>
Status:	CLOSED WONTFIX	QA Contact:	Mike McLean <mikem>
Severity:	high	Docs Contact:
Priority:	medium
Version:	rawhide	CC:	n3npq
Target Milestone:	---
Target Release:	---
Hardware:	All
OS:	Linux
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2006-02-03 16:21:39 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:

Description David Relson 2005-04-27 11:45:14 UTC

As bogofilter's lead developer I happened to have a DB_CONFIG file in the
directory when I ran "make rpm".  This causes 'rpm -qf' to fail.  rpm shouldn't
be looking in my current directory for DB_CONFIG!

[relson@osage tmp]$ rpm -q rpm
rpm-4.2.3-9mdk

[relson@osage tmp]$ rpm -qf /bin/bash
bash-3.0-2mdk

[relson@osage tmp]$ echo set_flags DB_LOG_AUTOREMOVE > DB_CONFIG

[relson@osage tmp]$ rpm -qf /bin/bash
error: cannot open Basenames index using db3 - Invalid argument (22)
error: cannot open Providename index using db3 - Invalid argument (22)
file /bin/bash is not owned by any package

### notice that creating DB_CONFIG in /tmp causes 'rpm -qf' to fail

Comment 1 Jeff Johnson 2006-02-03 16:21:39 UTC

This is configuration functionality, not a bug, provided by Berkeley DB.

"Don't do that." is the best answer.