[Date Prev][Date Next] [Thread Prev][Thread Next]
[Thread Index]
[Date Index]
[Author Index]
Re: error: rpmdbNextIterator: skipping h# 838 Header V3 DSA signature: BAD, key ID 30c9ecf8
- From: Michal Jaegermann <michal harddata com>
- To: For testers of Fedora Core development releases <fedora-test-list redhat com>
- Subject: Re: error: rpmdbNextIterator: skipping h# 838 Header V3 DSA signature: BAD, key ID 30c9ecf8
- Date: Sun, 1 Aug 2004 16:54:21 -0600
On Sun, Aug 01, 2004 at 03:43:26PM -0400, Robert Couture wrote:
> On Sun, 2004-01-08 at 12:56 -0500, Satish Balay wrote:
>
> > I've seen 'rpmdbNextIterator' messages & rpm misbehaving on a YLD/ppc box.
> > This was fixed after rebuilding rpmdb
> >
> > rm -f /var/lib/rpm/__db.*
> > rpmbuild --rebuilddb
> >
> > Not sure if this is the same issue - but you can give this a try.
>
> I got the error during rpm --rebuilddb three times ...
/var/lib/rpm/__db.* are "lock files" and you do not need them for
anything. They can be removed any time if you are not using rpm
in a way which modified other files.
All remaining file in /var/lib/rpm are "Berkeley DB" data base files
and there is a few utilities to deal with them with a documentation
residing in /usr/share/doc/db4-utils-4.2.52/utility/ on your test
system. Probably the most radical thing you can do to fix things
up is to use db_dump and pipe its output to db_load to write new
database files. Do such manipulations on copies! You can
always use '--root=...' option to tell rpm not to touch your
originals until things are back in order..
Michal
[Date Prev][Date Next] [Thread Prev][Thread Next]
[Thread Index]
[Date Index]
[Author Index]