Good afternoon, David,
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.
Simply do the upgrade, but upgrade them both at the same time
with:
rpm -Uvh glibc...rpm rpm...rpm
, i.e., both on the same command line. If even more packages are
required to satify dependencies (you'll probably need at least db1 and
db3), put them on the same command line. OK, you knew that.
If you're truly concerned that you won't be able to get back to
where you were, copy all of the files in the current rpm rpm ("rpm -ql
rpm" to see what they are) and all of the database files in /var/lib/rpm
to a backup directory. If something goes wrong, you can restore the
copies and start over.
From one of your previous messages:
> 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.
Good question. To the best of my experience with redhat - ~6 or
7 years - the only quirk with installing the rpm package is that I tend to
install it early on in an upgrade process. Other than that, it's pretty
much like any other rpm.
Cheers,
- Bill
---------------------------------------------------------------------------
Windows NT: n.
32-bit extensions and a graphical shell for a 16-bit patch to an 8-bit
operating system originally coded for a 4-bit microprocessor, written
by a 2-bit company that can't stand for 1 bit of competition.
(Courtesy of Michael Neuffer <[EMAIL PROTECTED]>)
--------------------------------------------------------------------------
William Stearns ([EMAIL PROTECTED]). Mason, Buildkernel, named2hosts,
and ipfwadm2ipchains are at: http://www.pobox.com/~wstearns
LinuxMonth; articles for Linux Enthusiasts! http://www.linuxmonth.com
--------------------------------------------------------------------------
_______________________________________________
Redhat-list mailing list
[EMAIL PROTECTED]
https://listman.redhat.com/mailman/listinfo/redhat-list
