On Thu, Sep 11, 2003 at 08:21:36AM +0200, Matthias Kurz wrote: > On Wed, Sep 10, 2003 at 10:36:10PM -0700, Conrad Steenberg wrote: > [...] > > Some suggestions (sorry if it sounds obvious :-) > Same here. > > 1. Make sure the openpkg rpm db is intact in the above directory
1. Wouldn't really know how to... This is a dir listing, but it's from a new ins tall of openpkg: $ ls -l /ebar/efs1/home1/s01/s011269/openpkg/local/RPM/DB total 4456 -rw-r--r-- 1 s011269 s01 24576 Sep 10 11:06 Basenames -rw-r--r-- 1 s011269 s01 49152 Sep 10 11:07 Conflictname -rw-r--r-- 1 s011269 s01 49152 Sep 10 11:07 Depends -rw-r--r-- 1 s011269 s01 16384 Sep 10 11:06 Dirnames -rw-r--r-- 1 s011269 s01 24576 Sep 10 11:06 Filemd5s -rw-r--r-- 1 s011269 s01 24576 Sep 10 11:06 Group -rw-r--r-- 1 s011269 s01 16384 Sep 10 11:06 Installtid -rw-r--r-- 1 s011269 s01 24576 Sep 10 11:06 Name -rw-r--r-- 1 s011269 s01 90112 Sep 10 11:06 Packages -rw-r--r-- 1 s011269 s01 24576 Sep 10 11:06 Providename -rw-r--r-- 1 s011269 s01 16384 Sep 10 11:06 Provideversion -rw-r--r-- 1 s011269 s01 24576 Sep 10 11:06 Pubkeys -rw-r--r-- 1 s011269 s01 24576 Sep 10 11:06 Requirename -rw-r--r-- 1 s011269 s01 16384 Sep 10 11:06 Requireversion -rw-r--r-- 1 s011269 s01 24576 Sep 10 11:06 Sha1header -rw-r--r-- 1 s011269 s01 24576 Sep 10 11:06 Sigmd5 -rw-r--r-- 1 s011269 s01 49152 Sep 10 11:07 Triggername -rw-r--r-- 1 s011269 s01 8192 Sep 10 11:05 __db.001 -rw-r--r-- 1 s011269 s01 1318912 Sep 10 11:06 __db.002 -rw-r--r-- 1 s011269 s01 417792 Sep 10 11:06 __db.003 -rw-r--r-- 1 s011269 s01 0 Sep 10 11:07 __db.004 -rw-r--r-- 1 s011269 s01 0 Sep 10 11:07 __db.005 -rw-r--r-- 1 s011269 s01 0 Sep 10 11:07 __db.006 -rw-r--r-- 1 s011269 s01 0 Sep 10 11:07 __db.007 -rw-r--r-- 1 s011269 s01 0 Sep 10 11:07 __db.008 -rw-r--r-- 1 s011269 s01 0 Sep 10 11:07 __db.009 > > 2. Make sure some other process isn't holding a lock on the db files 2. Don't really think so... I'm the only user, and it's pretty much my first action. Nothing seems to be locking it. > > 3. Check the permissions of the db directory, your user should have > > read and write access to the dir. 3. DB-dir: drwxr-xr-x 2 s011269 s01 4096 Sep 10 11:08 DB > > 4. Do an 'strace rpm -q openpkg' and send the output, that should show > > which system call failed (if the problem is in fact a permission or > > locking problem). > There is a strace command under Solaris, but it is probably better to > use "truss". > strace - print STREAMS trace messages > truss - trace system calls and signals 4. strace doesn't work "ERROR: unable to open /dev/log", but truss does though (output and some version of this mail can be found here: http://b0rken.dk/openpkg.txt ) > > 5. Make sure the right version of rpm gets called by your command. > That is a good idea, because there may be an /opt/sfw/bin/rpm from the > companion cd. 5. Already did that one... To convince you :) $ rpm --version RPM version 4.0 $ export PATH=/ebar/efs1/home1/s01/s011269/openpkg/local/bin/:$PATH $ rpm --version RPM version 4.2.1 Could this be a db problem (the program)? -- // Mark Gj�l Is it better to abide by the rules until they're changed or help speed the change by breaking them? -- http://b0rken.dk ______________________________________________________________________ The OpenPKG Project www.openpkg.org User Communication List [EMAIL PROTECTED]
