Bug 5129 - Updating rpmdrake brakes RPM DB
Summary: Updating rpmdrake brakes RPM DB
Status: RESOLVED DUPLICATE of bug 4918
Alias: None
Product: Mageia
Classification: Unclassified
Component: RPM Packages (show other bugs)
Version: Cauldron
Hardware: x86_64 Linux
Priority: Normal major
Target Milestone: ---
Assignee: Mageia Bug Squad
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2012-03-27 14:14 CEST by Fredrik Sandelin
Modified: 2012-03-27 14:20 CEST (History)
1 user (show)

See Also:
Source RPM: rpmdrake 5.32 1/mga2 noarch
CVE:
Status comment:


Attachments

Description Fredrik Sandelin 2012-03-27 14:14:44 CEST
Description of problem:
Making fresh install of Mageia 2 Beta 2. I select media sources, deselect the DVD and selecting "Core Release (distrib 1)" and "Core Updates (distrib 3)". Update rpmdrake to 5.32 1/mg2 noarch. After next try to update packages or install new ones getting the following error message:

A fatal error occured: Couldn't open RPM DB () at /usr/lib/perl5/vendor_perl/5.14.2/Rpmdrake/open_db.pm line 74.. 

Version-Release number of selected component (if applicable):
rpmdrake 5.32 1/mga2 noarch

How reproducible:
Did occur in Beta 1 and also in Beta 2, does occur every time, I have made 3 new installs.

Steps to Reproduce:
1. Install Mageia 2 Beta 2, without updating packages
2. Choose media sources, and update rpmdrake
3. Try to update again (any packages).

PS: In one Blog I read this problem would have been fixed, but I could not find any bug reporting this, and this problem still persist for me
Comment 1 Sander Lepik 2012-03-27 14:20:44 CEST
This problem is now fixed. But as beta2 is broken you need to do the first update with urpmi.

* add media sources (do not update rpmdrake with gui)
* from cli: urpmi --auto-update

After that everything should be OK.

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

Status: NEW => RESOLVED
CC: (none) => sander.lepik
Resolution: (none) => DUPLICATE


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