Bug 9748 - If mga2->3 upgrade fails with not enough free space rpm is broken in mga2 when trying to remove stuff
Summary: If mga2->3 upgrade fails with not enough free space rpm is broken in mga2 whe...
Status: RESOLVED WONTFIX
Alias: None
Product: Mageia
Classification: Unclassified
Component: Installer (show other bugs)
Version: Cauldron
Hardware: i586 Linux
Priority: Normal normal
Target Milestone: ---
Assignee: Thierry Vignaud
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks: 8016
  Show dependency tree / graph
 
Reported: 2013-04-15 21:21 CEST by claire robinson
Modified: 2013-05-01 22:09 CEST (History)
1 user (show)

See Also:
Source RPM:
CVE:
Status comment:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Description claire robinson 2013-04-15 21:21:52 CEST 
Trialing upgrades in vbox. HDD was too full for upgrade to take place so logged back in to mga2 to remove some stuff to find rpm broken.

error: db4 error(-30971) from dbenv->open: DB_VERSION_MISMATCH: Database environment version mismatch
error: cannot open Packages index using db4 -  (-30971)
error: cannot open Packages database in /var/lib/rpm
unable to open rpmdb



Reproducible: 

Steps to Reproduce:
claire robinson 2013-04-15 21:22:10 CEST

Summary: If mga2->3 upgrade fails with not enough free space rpm is broken in mga2 when to remove stuff => If mga2->3 upgrade fails with not enough free space rpm is broken in mga2 when trying to remove stuff

claire robinson 2013-04-15 21:22:37 CEST

Blocks: (none) => 8016

Comment 1 Thierry Vignaud 2013-04-16 20:51:06 CEST 
either removing /var/lib/rpm/__* or running "rpm --rebuilddb" should do the trick
Comment 2 claire robinson 2013-04-16 21:02:57 CEST 
Yep it did. Can it be prevented or is it just inevitable?
Comment 3 Thierry Vignaud 2013-04-16 21:51:59 CEST 
It cannot
Comment 4 Anne Nicolas 2013-05-01 22:00:59 CEST 
so closing that bug as WONTFIX ?

CC: (none) => ennael1

Comment 5 Thierry Vignaud 2013-05-01 22:09:12 CEST 
Yes

Status: NEW => RESOLVED
Resolution: (none) => WONTFIX
Note You need to log in before you can comment on or make changes to this bug.