Bug 156070 - conflict with DB_CONFIG
conflict with DB_CONFIG
Status: CLOSED WONTFIX
Product: Fedora
Classification: Fedora
Component: rpm (Show other bugs)
rawhide
All Linux
medium Severity high
: ---
: ---
Assigned To: Paul Nasrat
Mike McLean
:
Depends On:
Blocks:
  Show dependency treegraph
 
Reported: 2005-04-27 07:45 EDT by David Relson
Modified: 2007-11-30 17:11 EST (History)
1 user (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 2006-02-03 11:21:39 EST
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


Attachments (Terms of Use)

  None (edit)
Description David Relson 2005-04-27 07:45:14 EDT
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 11:21:39 EST
This is configuration functionality, not a bug, provided by Berkeley DB.

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

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