[Yum] glibc conflict question

[Peter Scott]

dear seth,

thanks for responding.  yes i fixed everything (laboriously)
using standard rpm --oldpackage commands.  turns out i had
(inadverently) two "testing" repos listed in /etc/yum.repos.d
that acted to make the "2.4.90-13" versions available via the
yum check-update command, so i thoughtlessly updated them.

now that everything is back to 2.4-8 (including glibc-devel)
gcc works fine.

of course i immediatly deleted the "testing" repos from the
yum.repos.d file (a good lesson for the day).

    -- peter

====================================================
On Aug 10, 2006 at 12:03 am, seth vidal wrote:
| On Wed, 2006-08-09 at 15:10 -0700, Peter Scott wrote:
| > 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.
| > 
| 
| There's no explicit conflict listed in the package. How would yum be
| able to know about it?
| 
| 
| > 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.)
| 
| and that would be the way to do it.
| 
| -sv
| 
| 
| _______________________________________________
| Yum mailing list
| Yum at lists.dulug.duke.edu
| https://lists.dulug.duke.edu/mailman/listinfo/yum
|