Bob,

I dislike this situation intensely, but I have been able to get around it by doing silly rpm tricks (like --nodeps and/or --force), or put all the circular RPMs on one command line:

   $ rpm -uvh rpm*.rpm glibc*.rpm pam*.rpm

and see what it does with that. I seem to remember doing this and having it work. Is there something wrong with doing it like this?

Troy

>>> tanner at real-time.com 05/18/01 02:43PM >>>
I got a G3 running YDL and I would like to upgrade glibc (this problem is not
specific to YDL).

Anyway, I got glibc-2.2.3 and I tried to update and there are lots of
dependencies that fail. There are many other packages that depend on the old
glibc-2.1, ok, irritating, but I understand.

On of these packages is pam, so I go get the latest pam, BUT it depends on
rpm 4.0 to be installed. Another irritation. :-)

Grabbed rpm 4.0, it depends on glibc-2.2.3! ARRGH! Circular dependencies.

Is my only choice to compile everything by hand?

-- 
Bob Tanner <tanner at real-time.com>       | Phone : (952)943-8700
http://www.mn-linux.org                 | Fax   : (952)943-8500
Key fingerprint =  6C E9 51 4F D5 3E 4C 66 62 A9 10 E5 35 85 39 D9 

_______________________________________________
tclug-list mailing list
tclug-list at mn-linux.org 
https://mailman.mn-linux.org/mailman/listinfo/tclug-list