On Thu, 2003-01-02 at 18:49, Michael Fratoni wrote:
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA1
>
> On Thursday 02 January 2003 07:37 pm, Cliff Wells wrote:
> > On Wed, 2003-01-01 at 17:57, Michael Fratoni wrote:
>
> > > If you look in /var/log/rpmpkgs, you should have a complete list of
>
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Thursday 02 January 2003 07:37 pm, Cliff Wells wrote:
> On Wed, 2003-01-01 at 17:57, Michael Fratoni wrote:
> > If you look in /var/log/rpmpkgs, you should have a complete list of
> > all the packages instaled on your system as of 4:00 AM today. If
On Wed, 2003-01-01 at 17:57, Michael Fratoni wrote:
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA1
>
> On Wednesday 01 January 2003 06:57 pm, Cliff Wells wrote:
> > I seem to have lost my rpm database. After upgrading a couple of rpms,
> > rpm would fail, telling me to run recover (whatever th
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Wednesday 01 January 2003 08:57 pm, Michael Fratoni wrote:
> The version of RPM included with the 8.0 release is prone to getting
> hung, and leaving the database in need of repair.
> http://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=73097
>
> Ge
Oddly enough, I had a similar problem on an smp development box
running Rawhide (beta) when I tried to upgrade to the new and
improved glibc set. Lots of "I can only do PRIVATE_DB" type
messages, rpm only worked from user accounts (not root) and no
ability to reverse the glibc change.
I ende
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Wednesday 01 January 2003 06:57 pm, Cliff Wells wrote:
> I seem to have lost my rpm database. After upgrading a couple of rpms,
> rpm would fail, telling me to run recover (whatever the hell that is -
> couldn't find any reference to such a thing i
On Wed, 2003-01-01 at 16:35, Roger wrote:
> Hi
>
> Try to do this
>
> rpm --rebuliddb
Already been tried (with a slightly different spelling ;) In fact, that
appears to be what killed my database to begin with).
Anyway, I seem to have gotten over the major hurdle. I used red-carpet
(which I no
Hi
Try to do this
rpm --rebuliddb
- Original Message -
From: "Cliff Wells" <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Sent: Thursday, January 02, 2003 7:57 AM
Subject: Corrupt rpm database
--
redhat-list mailing list
unsubscribe mailto:[EMAIL PROTECTE
I seem to have lost my rpm database. After upgrading a couple of rpms,
rpm would fail, telling me to run recover (whatever the hell that is -
couldn't find any reference to such a thing in the rpm man page).
Anyway, tried rpm --rebuilddb which also failed the first time, but
seemed to work the s
On Thursday 07 February 2002 08:34 pm, you wrote:
> > "Badger" == Badger <[EMAIL PROTECTED]> writes:
> You might want to try the rpm-list mailing list; it concentrates
> exclusively on RPM-related issues...
>
> You can signup here:
>
>https://listman.redhat.com/mailman/listinfo/r
> "Badger" == Badger <[EMAIL PROTECTED]> writes:
...
Badger> My rpm database is corrupt and I've tried both the "rpm
Badger> --rebuilddb," and the "rpm --initdb" and neither works. When I try
Badger> to install and rpm, do a rpm -qa, or rpm -Va, I get a segmentation
Badger> fault and the scr
Sorry if this is a re-post, the last post I sent on this subject went into a
rh mailing list "blackhole."
My rpm database is corrupt and I've tried both the "rpm --rebuilddb," and the
"rpm --initdb" and neither works. When I try to install and rpm, do a rpm
-qa, or rpm -Va, I get a segmentati
12 matches
Mail list logo
