[NTLUG:Discuss] RedHat 8 and broken rpm
Kelledin
kelledin+NTLUG at skarpsey.dyndns.org
Wed Dec 18 04:08:21 CST 2002
On Tuesday 17 December 2002 09:15 pm, Ryan Sweat wrote:
> I have RedHat 8 installed on 3 computers, and 2 of them (both
> intel i686) have broken rpm implementations. Almost everytime
> I attempt to install or remove a software package, the rpm
> command freezes and the database is corrupted. I have noticed
> by searching the redhat-lists and google that many people are
> having the same problem, but RedHat is dismissing it, saying
> they cannot reproduce it.
>
> I just wanted to see if anyone is having the same problem and
> what, if anything, you did to fix the problem. The way I get
> around it now is rm -f /var/lib/rpm/__*, and try again..and
> again..and again.
>
> Ryan
RedHat 8's using something close to glibc-2.3.1, right?
Last time I tried glibc-2.3.1, rpm-4.0.4 had similar problems
when building an RPM (not actually installing one, just
bootstrapping a source-based install in a chroot and building an
RPM package). It would sit and spin endlessly on my Alpha box,
and it would fail with an "Fseek" error on my x86 boxen. I
never tried rpm-4.1 and don't plan to, because rpm-4.1 breaks
the rpm API.
At that point, I just snorted in disgust and went back to
glibc-2.2.5 in order to make rpm happy. glibc-2.3.1 can wait
until it's more stable, or everything else is in sync with it.
In your case, that might mean going back to RedHat 7.x...or you
might try the new rpm-4.1. One or the other might solve your
problem.
--
Kelledin
"If a server crashes in a server farm and no one pings it, does
it still cost four figures to fix?"
More information about the Discuss
mailing list