At work I've got a RH 7.0 installation, which was a fresh, complete,
custom install, not an upgrade.
The other day I grabbed a whole pile of the updated RPMs for 7.0 that have
been released since the ISO images and went to try to install them.
For almost every one, RPM gave me an unresolved dependency on glibc 2.x.x.
Doing:
rpm -qa | grep libc
reports only ONE libc rpm installed, and that is the glibc-devel. I can
go look in /lib and SEE all the glibc .so files there. Besides, if they
weren't there the system wouldn't run anyway.
I did a --rebuilddb and it made no difference. I finally used --nodeps
to force install the updates. It all seems to work fine, but even after
installing all the glibc update packages it still thinks that there is no
glibc installed.
Is this a bug, or a feature? Does anyone know a fix?
Fred
--
---- Fred Smith -- [EMAIL PROTECTED] ----------------------------
The Lord detests the way of the wicked
but he loves those who pursue righteousness.
----------------------------- Proverbs 15:9 (niv) -----------------------------
_______________________________________________
Redhat-list mailing list
[EMAIL PROTECTED]
https://listman.redhat.com/mailman/listinfo/redhat-list
