| Summary: | mageia2b2, after updating drakrpm to 5.30, drakrpm fails | ||
|---|---|---|---|
| Product: | Mageia | Reporter: | episteme promeneur <epistemepromeneur> |
| Component: | RPM Packages | Assignee: | Mageia Bug Squad <bugsquad> |
| Status: | RESOLVED DUPLICATE | QA Contact: | |
| Severity: | normal | ||
| Priority: | release_blocker | CC: | alejandrocobo |
| Version: | Cauldron | ||
| Target Milestone: | --- | ||
| Hardware: | x86_64 | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Source RPM: | CVE: | ||
| Status comment: | |||
| Attachments: | drakrpm failure | ||
|
Description
episteme promeneur
2012-03-16 12:16:52 CET
Created attachment 1777 [details]
drakrpm failure
i can't install or update any software
episteme promeneur
2012-03-16 12:23:02 CET
Hardware:
i586 =>
x86_64
episteme promeneur
2012-03-16 12:23:28 CET
Priority:
Normal =>
release_blocker when itry to update in console with urpmi then [root@localhost ~]# urpmi --auto-update le média « Core Release » est à jour le média « Core Updates » est à jour le média « Nonfree Release » est à jour le média « Nonfree Updates » est à jour le média « Core 32bit Release » est à jour le média « Core 32bit Updates » est à jour erreur: rpmdb: Thread/process 3012/140241752344320 failed: Thread died in Berkeley DB library erreur: erreur db4(-30974) de dbenv->failchk: DB_RUNRECOVERY: Fatal error, run database recovery erreur: ne peut ouvrir l'index Packages en utilisant db4 - (-30974) erreur: impossible d'ouvrir la base de données Package dans /var/lib/rpm impossible d'ouvrir la base de donnée rpm [root@localhost ~]# Same problem here since some days ago in Cauldron and in the new Beta 2 under i586. CC:
(none) =>
alejandrocobo yes it appears during the last days of beta 1 the workaroud is to rebuil the rpm database [root@localhost ~]# rm -f /var/lib/rpm/__db* [root@localhost ~]# rpm --rebuilddb Thanks for the bug report. This particular issue has already been reported in our bug tracking system, but please feel free to report any further bugs you find. In general it is welcome to search for existing reports first to avoid filing duplicates. *** This bug has been marked as a duplicate of bug 4918 *** Status:
NEW =>
RESOLVED |