Bug 8752 - rpm-3.0.4-0.33.i386.rpm --rebuilddb corrupts database
Summary: rpm-3.0.4-0.33.i386.rpm --rebuilddb corrupts database
Alias: None
Product: Red Hat Raw Hide
Classification: Retired
Component: rpm
Version: 1.0
Hardware: i386
OS: Linux
Target Milestone: ---
Assignee: Jeff Johnson
QA Contact:
: 8993 (view as bug list)
Depends On:
TreeView+ depends on / blocked
Reported: 2000-01-22 23:53 UTC by dunwoody
Modified: 2008-05-01 15:37 UTC (History)
0 users

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Last Closed: 2000-01-24 17:03:21 UTC

Attachments (Terms of Use)

Description dunwoody 2000-01-22 23:53:37 UTC
I installed rpm-3.0.4-0.33.i386.rpm and ran rpm --rebuilddb, and
got the following messages:

    c130441-j:lib!> rpm --rebuilddb
    temporary database /var/lib/rpm already exists
    error creating directory /var/lib/rpm: File exists

Instead of creating a temp dir and rebuilding the database, rpm
apparently added to the existing database in /var/lib/rpm, resulting
in duplicates of everything in the database.  There may be a trivially
easy way to de-corrupt the database, but if so I don't know what
it is.

I backed off to rpm-3.0.4-0.31.i386.rpm and copied a good
/var/lib/rpm from another system, and the problem went away --
rpm --rebuilddb works fine again.

All of the rpms on the system exhibiting the problem were current
with the latest RawHide rpms as of Sat 2000/01/22 1200 PST.

Comment 1 Jeff Johnson 2000-01-23 23:11:59 UTC
Comment out the line in /usr/lib/rpm/macros that looks like
	%_rebuilddbpath         %{_dbpath}
This will be fixed in rpm-3.0.4-0.34.

Comment 2 Jeff Johnson 2000-01-24 17:03:59 UTC
Now fixed in rpm-3.0.4-0.34 from Raw Hide.

Comment 3 Eddy Cooper 2000-01-30 19:29:59 UTC
Is there a way to fix a database that was corrupted by already?  My database is
like 60 megs and has multiple copies of every package I've installed.  I'd like
to keep my current database cause I've installed quite a few things since the
problems started....

Comment 4 Jeff Johnson 2000-01-31 16:03:59 UTC
*** Bug 8993 has been marked as a duplicate of this bug. ***

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