On Wed, 29 Nov 2000, David Ruggiero wrote:
>
> Thanks for the amazingly quick response, guys, but no one seemed to have
> really understood my concern, or at least addressed it in their replies. So
> I'll try again (please read carefully). I wrote:
>
> >SO...long story short, I can't install glibc because it will break rpm,
> >BUT if I install the new RPM first, it will fail because I've still got
> >the old glibc, and I'll have no way to install the new one, because I need
> >a working "rpm" to do that....<sigh>
>
> To spell it out: Yes, I KNOW I can use --nodeps to force installation, and
> "-U" to upgrade a package instead of "-i" to install it.. (I've RTFM.)
> That's not the point. My worry is that if I DO force installation of one or
> more of the packages involved, I'll break RPM and then not be able to
> install anything at all afterwards - including any packages that might dig
> me out of that hole.
>
> If someone has *specific* advice that involves this sort of problem WHEN
> RPM IS ONE OF THE PACKAGES INVOLVED IN THE DEPENDENCY CONFLICT (please read
> that sentence again), I'm all ears. Thanks.
>
rpm -Uvh rpm-<some version> glibc-<some version>
Trust me, this is the ONLY way to install two files that
depend on each other. Now, you may also find OTHER
dependencies as well.... which you'll need to solve, but
you can just download them and add them to the same command
line... good luck!
John
PS... please tell Eudora to ONLY post to this list in
plain, ascii text. :-) Thanks
_______________________________________________
Redhat-list mailing list
[EMAIL PROTECTED]
https://listman.redhat.com/mailman/listinfo/redhat-list
