I have recently upgraded glibc, glibc-common and glibc-headers from version 2.4-8 to 2.4.90-13, having run yum check-update and finding these on the output. However a consequence was that gcc would no longer work properly, failing at the loader (linker) stage. The reason appears to be that glibc-devel, which is normally used by gcc, does not yet seem to have been upgraded to 2.4.90-13, so there is a conflict, which was not detected by yum. Is there a convenient way to UNDO the updating, i.e., to re-install version 2.4-8 for the glibc* packages already installed on my machine? (This would be the equivalent of rpm -Uvh --oldpackage glibc-2.4-8....rpm etc.) (I am reluctant to fool around too much with glibc since almost everything depends on it.) I am running FC5; the output from uname -a is Linux localhost.localdomain 2.6.17-1.2139_FC5 #1 SMP Fri Jun 23 12:40:11 EDT 2006 x86_64 x86_64 x86_64 GNU/Linux My list of yum repositories is dries.repo fedora-core.repo fedora-development.repo fedora-extras-development.repo fedora-extras.repo fedora-legacy.repo fedora-updates-testing.repo fedora-updates.repo freshrpms.repo livna-devel.repo livna-testing.repo livna.repo macromedia.repo (maybe i should disable the "testing" repos?)
