From: Samuel Flory <sflory@rackable.com>
To: Bradley Chapman <kakadu_croc@yahoo.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: 2.6.0-test5 broke RPM 4.2 on Red Hat 9 in a VERY weird way
Date: Fri, 26 Sep 2003 08:53:18 -0700 [thread overview]
Message-ID: <3F7460EE.1070002@rackable.com> (raw)
In-Reply-To: <20030926075004.79990.qmail@web40903.mail.yahoo.com>
Bradley Chapman wrote:
> Mr. Flory,
>
> --- Samuel Flory <sflory@rackable.com> wrote:
>
>>Bradley Chapman wrote:
>>
>>>Damn, spoke too soon :(
>>>
>>>I upgraded to popt 1.8.1, installed beecrypt (rawhide RPM needs it), and
>>
>>installed
>>
>>>rpm 4.2.1 from rawhide -- all using LD_ASSUME_KERNEL=2.2.5. Reloaded my konsole
>>>to clear&reset my environment.
>>>
>>>Now I still get the error, but the program still works, i.e. something like
>>
>>this:
>>
>>>rpm -qpl /download/system/popt-1.8.1-0.30.i386.rpm
>>>rpmdb: unable to join the environment
>>>error: db4 error(11) from dbenv->open: Resource temporarily unavailable
>>>error: cannot open Packages index using db3 - Resource temporarily unavailable
>>
>>(11)
>>
>>>error: cannot open Packages database in /var/lib/rpm
>>>warning: /download/system/popt-1.8.1-0.30.i386.rpm: V3 DSA signature: NOKEY, key
>>
>>ID
>>
>>>897da07a
>>>/usr/include/popt.h
>>>/usr/lib/libpopt.a
>>>/usr/lib/libpopt.la
>>>/usr/lib/libpopt.so
>>>/usr/lib/libpopt.so.0
>>>/usr/lib/libpopt.so.0.0.0
>>>/usr/share/locale/cs/LC_MESSAGES/popt.mo
>>>/usr/share/locale/da/LC_MESSAGES/popt.mo
>>>/usr/share/locale/de/LC_MESSAGES/popt.mo
>>>/usr/share/locale/es/LC_MESSAGES/popt.mo
>>>/usr/share/locale/eu_ES/LC_MESSAGES/popt.mo
>>>/usr/share/locale/fi/LC_MESSAGES/popt.mo
>>>/usr/share/locale/fr/LC_MESSAGES/popt.mo
>>>/usr/share/locale/gl/LC_MESSAGES/popt.mo
>>>/usr/share/locale/hu/LC_MESSAGES/popt.mo
>>>/usr/share/locale/id/LC_MESSAGES/popt.mo
>>>/usr/share/locale/is/LC_MESSAGES/popt.mo
>>>/usr/share/locale/it/LC_MESSAGES/popt.mo
>>>/usr/share/locale/ja/LC_MESSAGES/popt.mo
>>>/usr/share/locale/ko/LC_MESSAGES/popt.mo
>>>/usr/share/locale/no/LC_MESSAGES/popt.mo
>>>/usr/share/locale/pl/LC_MESSAGES/popt.mo
>>>/usr/share/locale/pt/LC_MESSAGES/popt.mo
>>>/usr/share/locale/pt_BR/LC_MESSAGES/popt.mo
>>>/usr/share/locale/ro/LC_MESSAGES/popt.mo
>>>/usr/share/locale/ru/LC_MESSAGES/popt.mo
>>>/usr/share/locale/sk/LC_MESSAGES/popt.mo
>>>/usr/share/locale/sl/LC_MESSAGES/popt.mo
>>>/usr/share/locale/sr/LC_MESSAGES/popt.mo
>>>/usr/share/locale/sv/LC_MESSAGES/popt.mo
>>>/usr/share/locale/tr/LC_MESSAGES/popt.mo
>>>/usr/share/locale/uk/LC_MESSAGES/popt.mo
>>>/usr/share/locale/wa/LC_MESSAGES/popt.mo
>>>/usr/share/locale/zh/LC_MESSAGES/popt.mo
>>>/usr/share/locale/zh_CN.GB2312/LC_MESSAGES/popt.mo
>>>/usr/share/man/man3/popt.3.gz
>>>
>>>Anybody have any other ideas?
>>>
>>
>>
>> Try a "LD_ASSUME_KERNEL=2.2.5 rpm --rebuilddb"?
>
>
> Excellent! Thanks for the advice; now it works perfectly fine.
>
Most likely you screwed up the rpm database durning your prior
problems.
--
Once you have their hardware. Never give it back.
(The First Rule of Hardware Acquisition)
Sam Flory <sflory@rackable.com>
prev parent reply other threads:[~2003-09-26 16:00 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-09-25 21:23 2.6.0-test5 broke RPM 4.2 on Red Hat 9 in a VERY weird way Bradley Chapman
2003-09-25 23:23 ` Samuel Flory
2003-09-26 7:50 ` Bradley Chapman
2003-09-26 15:53 ` Samuel Flory [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=3F7460EE.1070002@rackable.com \
--to=sflory@rackable.com \
--cc=kakadu_croc@yahoo.com \
--cc=linux-kernel@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).