2:26 p.m.
I managed to axe my rpm database while attempting to fix my segmentation
fault problems yesterday. Essentially, rpm -qa is now coming up blank,
rpm --rebuilddb nor rpm --initdb doesn't seem to fix anything. Anything
else? I tried re-installing the rpms for rpm-* and rpmdb-, but to no
avail. Any suggestions?
Tony
3:01 p.m.
Tony Perrie wrote:
I managed to axe my rpm database while attempting to fix my
segmentation
fault problems yesterday. Essentially, rpm -qa is now coming up blank,
rpm --rebuilddb nor rpm --initdb doesn't seem to fix anything. Anything
else? I tried re-installing the rpms for rpm-* and rpmdb-, but to no
avail. Any suggestions?
<?>
# rm -f /var/lib/rpm/__db.00*
</?>
--
shrek-m
4:58 p.m.
Yeah, I tried that. I think I wiped out the headers or something.
--rebuilddb isn't work regardless of what's in /var/lib/rpm.
Tony
On Thu, 3 Jun 2004, shrek-m(a)gmx.de wrote:
Tony Perrie wrote:
>I managed to axe my rpm database while attempting to fix my segmentation
>fault problems yesterday. Essentially, rpm -qa is now coming up blank,
>rpm --rebuilddb nor rpm --initdb doesn't seem to fix anything. Anything
>else? I tried re-installing the rpms for rpm-* and rpmdb-, but to no
>avail. Any suggestions?
>
>
<?>
# rm -f /var/lib/rpm/__db.00*
</?>
--
5:07 p.m.
On Thu, Jun 03, 2004 at 04:58:54PM -0500, Tony Perrie wrote:
Yeah, I tried that. I think I wiped out the headers or something.
--rebuilddb isn't work regardless of what's in /var/lib/rpm.
If you have the current list (say in /var/log/rpmpkgs) then you can
re-construct the whole thing from scratch with a help of '--justdb'
option to rpm. Depending on from where you need to pull packages it
may be a fair amount of work.
Michal
7:21 p.m.
----- Original Message -----
From: <shrek-m(a)gmx.de>
To: "For testers of Fedora Core development releases"
<fedora-test-list(a)redhat.com>
Sent: Thursday, June 03, 2004 4:01 PM
Subject: Re: RPM Database Problems
Tony Perrie wrote:
>I managed to axe my rpm database while attempting to fix my segmentation
>fault problems yesterday. Essentially, rpm -qa is now coming up blank,
>rpm --rebuilddb nor rpm --initdb doesn't seem to fix anything. Anything
>else? I tried re-installing the rpms for rpm-* and rpmdb-, but to no
>avail. Any suggestions?
>
>
<?>
# rm -f /var/lib/rpm/__db.00*
</?>
--
shrek-m
If your "rpm --rebuilddb" is actually functioning and completing, you
probably don't need to do that. That remove step is more helpful when rpm is
wedged and confused and won't allow any rpm queries or operations
whatsoever, which I've run into on occasion. (The handshaking and queue-ing
that allows you to do simultaneous rpm operations is not perfect.)
11:04 p.m.
been there, done that, about the only thing you can do is to re-install
all the rpms with the --justdb option
shrek-m(a)gmx.de wrote:
Tony Perrie wrote:
> I managed to axe my rpm database while attempting to fix my
> segmentation fault problems yesterday. Essentially, rpm -qa is now
> coming up blank, rpm --rebuilddb nor rpm --initdb doesn't seem to fix
> anything. Anything else? I tried re-installing the rpms for rpm-*
> and rpmdb-, but to no avail. Any suggestions?
>
>
<?>
# rm -f /var/lib/rpm/__db.00*
</?>
2:36 a.m.
On Thu, Jun 03, 2004 at 09:04:34PM -0700, Bruce Ferrell wrote:
been there, done that, about the only thing you can do is to
re-install
all the rpms with the --justdb option
You'll want to use --notriggers and --noscripts to to prevent unwanted things
happening as you rebuild the db.
Paul
7274
days inactive
7275
days old
6 comments
6 participants
participants (6)
-
Bruce Ferrell -
Michal Jaegermann -
Nico Kadel-Garcia -
Paul Nasrat -
shrek-m＠gmx.de -
Tony Perrie