> Thats an extremely off experience here statement . Yum has updated > glibc once on this box that I know of. No problems caused by that. > But every time it tries to put in a newer python libxml2, it breaks > itself and half the rest of the system that uses python till I go > back to the FC2 cd's and forceably reinstall the originals again. If > the writers of libxml2 cannot make a new version backwards > compatible, I would much prefer it be left the hell alone until all > the stuff that depends on it have also been updated to be compatible. > > I've had a severely crippled machine for 3 of the 6 months I've been > running FC2. And questions sent here as to why have, with one or two > exceptions, been met with the usual phone support lets take it by the > numbers order of troubleshooting that degenerates into a 'Gee, thats > never happened here' quote, and I'm left hanging. Once I figured out > that if I put the CD's versions back in, I've been able to fix it > everytime yum fubars it. But I eventually got tired of that and now > thats in the exclude list in my yum.conf. Gene, I've seen your messages to yum-list and fedora lists. In almost every case you've installed things via check-install and your rpmdb is bordering on spaghetti. Your problems with yum are entirely user error. -sv