On Wed, 29 Nov 2000, David Ruggiero wrote:
>
> Today's fun and games:
>
> Okay, so I want to upgrade to the newest version of "patch", which I
> apparently need for some of the latest-and-greatest kernel patches. (This
> is for my firewall machine - generic RH6.2 with a fairly-current 2.2.17
> kernel from rawhide rpms, necessary because I need IPSEC support) So I
> snarf the "patch" package's .rpm and try an install:
>
[snip]
>
>
> 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>
>
> What do people do in chicken-and-egg situations like this? I'm all ears for
> a solution (a pointer to an appropriate net.resource is fine, too).
>
> thanks,
> David
>
> PS: I know that RPM is pretty good at figuring out dependencies, etc, if
> you give it all packages to be upgraded at once shot (ie, "rpm -ivh *.rpm).
> But I figure that may not apply here, where one of the packages to be
> installed *IS* rpm itself.
>
First off, would you mind NOT posting in HTML? Not everyone
can read it...
Now, onto your question. Try putting BOTH rpm and glibc on
the same command line. That's the ONLY way to install rpm
files that depend on each other.
John
_______________________________________________
Redhat-list mailing list
[EMAIL PROTECTED]
https://listman.redhat.com/mailman/listinfo/redhat-list
