Bugzilla will be upgraded to version 5.0 on a still to be determined date in the near future. The original upgrade date has been delayed.
Bug 26015 - Unable to run rpm -q --redhatprovides
Unable to run rpm -q --redhatprovides
Status: CLOSED DUPLICATE of bug 22911
Product: Red Hat Linux
Classification: Retired
Component: rpm (Show other bugs)
i386 Linux
medium Severity medium
: ---
: ---
Assigned To: Jeff Johnson
David Lawrence
Depends On:
  Show dependency treegraph
Reported: 2001-02-04 19:47 EST by adam.huffman
Modified: 2007-04-18 12:31 EDT (History)
0 users

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2001-02-15 11:43:52 EST
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 adam.huffman 2001-02-04 19:47:02 EST
The cause of this problem might be that the rpm package has not been
installed correctly:

rpm -V rpm
missing    /etc/rpm/macros.db1

that's after re-installing it.

I was having problems installing the XEmacs RPM, owing to failed
dependencies, so I tried rpm -q --redhatprovides libwnn6.so.1.0
but I got the following error message:

error: cannot open Packages index using db3 - No such file or directory (2)

rpm -V rpmdb-redhat doesn't produce any errors
Comment 1 Jeff Johnson 2001-02-05 10:59:35 EST
       rpm -V rpm
       missing    /etc/rpm/macros.db1
verification is as expected, as /etc/rpm/macros.db1 is removed in %post if
using db3 in rpm.

Adding "--dbapi 1" will permit querying db1 databases such as what's in rpmdb.
Comment 2 adam.huffman 2001-02-05 21:31:09 EST
It might be nice to document this.
Comment 3 Jeff Johnson 2001-02-07 12:59:58 EST
Yes it would be nice to document, the issue is where it should be documented so
the information can be found.
Comment 4 Matt Wilson 2001-02-15 11:46:49 EST

*** This bug has been marked as a duplicate of 22911 ***

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