Bug 5081

Summary: Impossible to update the system after the update from Mga 1 to Mga 2 b2
Product: Mageia Reporter: Marcello Anni <marcello.anni>
Component: RPM PackagesAssignee: Mageia Bug Squad <bugsquad>
Status: RESOLVED DUPLICATE QA Contact:
Severity: major    
Priority: Normal    
Version: Cauldron   
Target Milestone: ---   
Hardware: i586   
OS: Linux   
Whiteboard:
Source RPM: urpmi CVE:
Status comment:

Description Marcello Anni 2012-03-24 21:04:02 CET 
Description of problem:
hi,

i've update my system from mageia 1 to mageia 2 beta 2. after the upgrade, i can't update anymore the system.

here is the log i receive:

[root@localhost ~]# urpmi --auto-update
il supporto "Core Release (distrib1)" risulta già aggiornato
il supporto "Nonfree Release (distrib11)" risulta già aggiornato
il supporto "Tainted Release (distrib21)" risulta già aggiornato
il supporto "Core Updates (distrib3)" risulta già aggiornato
il supporto "Nonfree Updates (distrib13)" risulta già aggiornato
il supporto "Tainted Updates (distrib23)" risulta già aggiornato
errore: rpmdb: Thread/process 31936/3074066112 failed: Thread died in Berkeley DB library
errore: db4 errore(-30974) da dbenv->failchk: DB_RUNRECOVERY: Fatal error, run database recovery
errore: impossibile aprire l'indice Packages utilizando db4 -  (-30974)
errore: impossibile aprire il database dei pacchetti in /var/lib/rpm
impossibile aprire il database rpm



cheers,
Marcello
Comment 1 Manuel Hiebel 2012-03-24 21:33:11 CET 
you have use the online media or the dvd for make the upgrade ?
if it's with the dvd, it's a duplicate of bug 4918

Keywords: (none) => NEEDINFO

Comment 2 Marcello Anni 2012-03-25 13:01:30 CEST 
i've used the dvd to make the upgrade. now that i remember, after the upgrade it worked well, only after the update of urpmi components (after the upgrade) the issue occurrs. i've followed the instructions of this comment https://bugs.mageia.org/show_bug.cgi?id=4918#c81 and i resolved. do we consider this bug as closed?

Keywords: NEEDINFO => (none)

Comment 3 Manuel Hiebel 2012-03-25 14:17:01 CEST 
yep thanks

*** This bug has been marked as a duplicate of bug 4918 ***

Status: NEW => RESOLVED
Resolution: (none) => DUPLICATE