On Tue, 2002-01-15 at 16:32, Devon wrote: > -----BEGIN PGP SIGNED MESSAGE----- > Hash: SHA1 > > On Tuesday 15 January 2002 03:43 pm, James Pifer wrote: > > Sorry if this gets double posted but the one I wrote a while ago still > > hasn't made the list.... > > > I can't seem to upgrade any RPM's with the -U option. I have never seen > > this work. Should it work? > > Yes, if done correctly. ;) > > > So I've been using -i --force. Most of the time this works. > > Hrmm, I wouldn't, but it is your machine. > > > I've updated OpenSSL because OpenSSH required it. Now I'm trying to > > upgrade glibc. When I try to do glibc-2.2.4-13 it says it fails > > dependencies for glibc-devel. If I try to upgrade glibc-devel to > > 2.2.4-13 it say it needs glibc-2.2.4-13. Isn't this a catch 22? How the > > heck should I be doing these upgrades? > > Packages that depend on each other should be upgraded together. > It has always worked for me. For example, to upgrade glibc, just put all > the new packages in the same location, and do: > rpm -Uvh glib*.rpm
Just a note. rpm -U will install a package that is not installed in addition to upgrading the ones that are there. rpm -F will only upgrade installed packages. I keep an NFS mounted software repository on my internal network and periodically cd to it and do rpm -Fvh * This upgrades all packages that are in the directory if they are installed on the machine. Bret _______________________________________________ Redhat-list mailing list [EMAIL PROTECTED] https://listman.redhat.com/mailman/listinfo/redhat-list
