So actually the db_recovery docs already separate BDB from the other cases,
with instructions on how to tell which one is being used.
Support for BDB databases has been removed entirely in more recent rpm versions
so there's nothing we can do about this now. And note that the "locks grouped
Closed #2320 as completed.
--
Reply to this email directly or view it on GitHub:
https://github.com/rpm-software-management/rpm/issues/2320#event-8037518590
You are receiving this because you are subscribed to this thread.
Message ID:
___
Rpm-maint
Oh, that db_recovery stuff is only relevant for Berkeley DB backend, and in
upstream configuration. On Suse, the BDB usage differs and you wouldn't see
such messages (IIRC). Also 4.14 fell out of upstream support a couple of years
ago already.
The db_recovery doc needs to be updated though.
solved it by running
`rpmdb --rebuilddb`
as written in docs. For me it was hard to find the right backup strategy, as
some parts of https://rpm.org/user_doc/db_recovery.html would not work:
```
pcmsi-i7-4790k:/usr/lib/sysimage/rpm # /usr/lib/rpm/rpmdb_stat -CA
rpmdb_stat: DB_ENV->open: No such
Currently i have:
```
pcmsi-i7-4790k:~ # rpm -qa wine
wine-7.21-lp154.1505.2.x86_64
wine-7.22-lp154.970.1.x86_64
pcmsi-i7-4790k:~ #
```
well it IS only installed once, so this is strange as such.
i remove the one existing version
```
pcmsi-i7-4790k:~ # rpm -ev wine-7.22-lp154.970.1.x86_64
