Bug 2139

Summary:	rpm upgrade does not rebuild the rpm database
Product:	[Retired] Red Hat Raw Hide	Reporter:	Need Real Name <aander07>
Component:	rpm	Assignee:	Jeff Johnson <jbj>
Status:	CLOSED WORKSFORME	QA Contact:
Severity:	medium	Docs Contact:
Priority:	medium
Version:	1.0	CC:	gafton
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:	1999-04-17 17:42:36 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 Need Real Name 1999-04-12 14:54:32 UTC

After upgrading rpm from 2.5.5-5.2 to 2.94-6, any freshen
(-F) operations would fail silently, as though there were
nothing to upgrade.

Running an upgrade (-U) gave the message that the rpm
database needed to be rebuilt due to database changes.

After a database rebuild, the previous freshen operation
worked as expected.

Comment 1 Cristian Gafton 1999-04-12 16:30:59 UTC

jeff, maybe this could be done as a postinstall thingie ?

Comment 2 Jeff Johnson 1999-04-12 17:25:59 UTC

We don't do a --rebuilddb in the rpm %post for two reasons:
1) it normally isn't needed. The current change to a hashed
db is done once and once only.
2) the disk space and time requirements for installing rpm
would become indeterminate.