Bug 8216 - cannot open RPM DB
Summary: cannot open RPM DB
Status: RESOLVED OLD
Alias: None
Product: Mageia
Classification: Unclassified
Component: RPM Packages (show other bugs)
Version: 2
Hardware: i586 Linux
Priority: Normal normal
Target Milestone: ---
Assignee: Mageia Bug Squad
QA Contact:
URL:
Whiteboard:
Keywords: NEEDINFO
Depends on:
Blocks:
 
Reported: 2012-11-27 02:41 CET by George DeLoach
Modified: 2013-11-23 16:16 CET (History)
3 users (show)

See Also:
Source RPM: rpmdrake
CVE:
Status comment:


Attachments

Description George DeLoach 2012-11-27 02:41:03 CET
Recently when I tried to run an update on my computer, I received the following error message:

"A fatal error occurred: Couldn't open RPM DB )_ at /usr/lib/perl5/vendor_perl/5.12.2/Rpmdrake/open_db line 74 . ."

I did a quick web search, and found that this topic had appeared in an April 2012 post in the testing section as follows:

https://forums.mageia.org/en/viewtopic.php?f=8&t=2216

I followed the steps set forth in the forum post, and I successfully re-installed my rpm database.  However, I wanted to note the bug apparently re-surfaced in my installation, which was NOT a beta version.
Comment 1 George DeLoach 2012-11-27 02:52:38 CET
One other thing that occurred to me when I submitted this bug- I installed my copy of Mageia 2 from a DVD which shipped with Issue No. 162 of "Linux Format" magazine.  So far as I can tell, this was not a beta version on the disk, and I ran a full update of all packages once I installed the distro on my desktop computer.  This bug also affected the Apper KDE installer, which refused to update until I reinstalled the rpm database.
Comment 2 Thierry Vignaud 2012-11-27 11:41:49 CET
This has nothing to do with an older bug.
There can be many reasons why rpm db cannot be opened.
We need more info.

Keywords: (none) => NEEDINFO
CC: (none) => thierry.vignaud
Summary: A beta 2 bug involving the RPM db appears to have reappeared in my installation of Mageia 2 => cannot open RPM DB
Source RPM: (none) => rpmdrake

Comment 3 roelof Wobben 2013-01-07 15:49:32 CET
Can anyone confirm this bug ?

Roelof

CC: (none) => r.wobben

Walter Martini 2013-06-24 22:24:23 CEST

CC: (none) => wtr

Comment 4 Manuel Hiebel 2013-10-22 12:19:59 CEST
This message is a reminder that Mageia 2 is nearing its end of life.
Approximately one month from now Mageia will stop maintaining and issuing updates for Mageia 2. At that time this bug will be closed as WONTFIX (EOL) if it remains open with a Mageia 'version' of '2'.

Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Mageia version prior to Mageia 2's end of life.

Bug Reporter: Thank you for reporting this issue and we are sorry that we may not be able to fix it before Mageia 2 is end of life.  If you would still like to see this bug fixed and are able to reproduce it against a later version of Mageia, you are encouraged to click on "Version" and change it against that version of Mageia.

Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Mageia release includes newer upstream software that fixes bugs or makes them obsolete.

-- 
The Mageia Bugsquad
Comment 5 Manuel Hiebel 2013-11-23 16:16:09 CET
Mageia 2 changed to end-of-life (EOL) status on ''22 November''. Mageia 2 is no
longer maintained, which means that it will not receive any further security or
bug fix updates. As a result we are closing this bug.

If you can reproduce this bug against a currently maintained version of Mageia
please feel free to click on "Version" change it against that version of Mageia
and reopen this bug.

Thank you for reporting this bug and we are sorry it could not be fixed.

--
The Mageia Bugsquad

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


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