pld rpm 5.4.17

[Jeffrey Johnson]

> On Jan 10, 2017, at 2:49 PM, Jeffrey Johnson <n3npq at me.com> wrote:
> 
>> 
>> On Jan 10, 2017, at 2:36 PM, Elan Ruusamäe <glen at pld-linux.org <mailto:glen at pld-linux.org>> wrote:
>> 
>> not cool.
>> 
> 
> You (likely) have misbuilt  rpm somehow, likely by picking up
> 	#include <db.h>
> in /usr/include rather than the version specific db.h using -I/usr/include/dbXY.
> 
>> $ rpm -q rpm
>> BDB0056 DB->cursor: DB_READ_COMMITTED, DB_READ_UNCOMMITTED and DB_RMW require locking
>> error: db3copen:db3.c:1470: db->cursor(22): Invalid argument
>> BDB0056 DB->cursor: DB_READ_COMMITTED, DB_READ_UNCOMMITTED and DB_RMW require locking
>> error: db3copen:db3.c:1470: db->cursor(22): Invalid argument
>> BDB0630 DB_THREAD mandates memory allocation flag on primary key DBT
>> error: db3cpget:db3.c:1568: db->pget(22): Invalid argument
>> error: error(22) getting keys from Nvra index
>> error: error(1) getting records from Nvra index
>> package rpm is not installed
>> 

Another possibility is that your Berkeley DB needs locking: my guess above is based on experience only,
and its impossible to diagnose without more info.

(aside)
db3.c is known to work with many many versions of Berkeley DB, and there has been
no change in the rpmdb code for 5+ years. YMMV (and clearly does).

73 de Jeff