RPM

5.3.4: DB_CONFIG issues

Bug #647604 reported by Jeff Johnson
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
RPM
Confirmed
Low
Unassigned

Bug Description

Using DB_CONFIG to configure an rpmdb has (Berkeley DB) version dependencies.

Here's one issue (noted on an IDMS install)

 361:syslog-ng ########################################### [ 90%]
rpmdb: unrecognized name-value pair: set_create_dir
rpmdb: unrecognized name-value pair: set_create_dir
error: db4 error(22) from dbenv->open: Invalid argument
error: cannot open Packages(0) index using db3 - Invalid argument (22)
error: cannot open Packages database in /var/lib/rpm
/X/src/wdj53/tests/tmp/rpm-tmp.71493: line 2: [: too many arguments
 362:yum-updatesd ########################################### [ 90%]

Ultimately this is a packaging problem:
    Why should packages be attempting anything with an rpmdb?
Yes, I know the answers ...

Jeff Johnson (n3npq)
summary: - 5.3.4: DB_CONFIXG issues
+ 5.3.4: DB_CONFIG issues
Changed in rpm:
status: New → Confirmed
importance: Undecided → Low
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.