Bug 2139 - rpm upgrade does not rebuild the rpm database
Summary: rpm upgrade does not rebuild the rpm database
Status: CLOSED WORKSFORME
Alias: None
Product: Red Hat Raw Hide
Classification: Retired
Component: rpm
Version: 1.0
Hardware: All
OS: Linux
medium
medium
Target Milestone: ---
Assignee: Jeff Johnson
QA Contact:
URL:
Whiteboard:
Keywords:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 1999-04-12 14:54 UTC by Need Real Name
Modified: 2008-05-01 15:37 UTC (History)
1 user (show)

(edit)
Clone Of:
(edit)
Last Closed: 1999-04-17 17:42:36 UTC


Attachments (Terms of Use)

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.


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