Bug 504253 - Urgent Problem Upgrading from rpm 4.6.0-10.fc10 to 4.6.1-1.fc10
Urgent Problem Upgrading from rpm 4.6.0-10.fc10 to 4.6.1-1.fc10
Status: CLOSED NOTABUG
Product: Fedora
Classification: Fedora
Component: rpm (Show other bugs)
10
All Linux
low Severity urgent
: ---
: ---
Assigned To: Panu Matilainen
Fedora Extras Quality Assurance
:
Depends On:
Blocks:
  Show dependency treegraph
 
Reported: 2009-06-05 02:01 EDT by Eli Wapniarski
Modified: 2009-06-05 02:42 EDT (History)
3 users (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 2009-06-05 02:12:21 EDT
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


Attachments (Terms of Use)

  None (edit)
Description Eli Wapniarski 2009-06-05 02:01:36 EDT
!!!!! PANU !!!!!

I'm afraid now to upgrade from F-10 to F-11. Please tell me that this won't be a problem.

Upgrading from rpm  4.6.0-10.fc10  to 4.6.1-1.fc10 represents a downgrade to the version of the database used.

Reason that this particular version was installed was to deal with a problem with synaptic.

I had a backup of everything so I'm OK. But other users who ran into this and 

rpm --rebuilddb
rpmdb: PANIC: fatal region error detected; run recovery
error: db4 error(-30975) from dbenv->open: DB_RUNRECOVERY: Fatal error, run database recovery
error: cannot open Packages index using db3 -  (-30975)

This one is VERY VERY URGENT as other users could be faced with a broken rpm system with no easy way to recover.
Comment 1 Panu Matilainen 2009-06-05 02:12:21 EDT
Rpm in F10 has been built with DB 4.5 all the time, so people using official F10 packages aren't affected. Glad you had a backup, but just FYI it is possible to downgrade the db format with db_dump + db45_load.
Comment 2 Eli Wapniarski 2009-06-05 02:42:08 EDT
Thank you for your very quick response.

How will this issue affect the upgrade from F-10 to F-11?

(In reply to comment #1)
> Rpm in F10 has been built with DB 4.5 all the time, so people using official
> F10 packages aren't affected. Glad you had a backup, but just FYI it is
> possible to downgrade the db format with db_dump + db45_load.  

Be that as it may. Those of us that, per your instructions, rebuild our own from rawhide to deal with synaptic problem are very much likely to screw up the rpm database before they have a chance to downgrade. Please take this into account.


How will downgrading the database affect the functionality of synaptic?

Could you kindly provide more detailed instructions on how to get the database downgraded?

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