Prev: CentOS4.6; yum spontaneously broke (libxml2mod.so undef. symbol xmlNewDocPI)
Next: how to configure static route on RHEL 3 AS
From: Nico Kadel-Garcia on 25 Apr 2008 19:37 Damon Getsman wrote: > On Apr 24, 1:43 pm, Damon Getsman <dgets...(a)amirehab.net> wrote: >> So I break out yum and begin searching for something that will provide >> that. But it doesn't go very far, because out of nowhere 'yum' comes >> back with: >> >> -=-=-=-=-=-=- >> There was a problem importing one of the Python modules >> required to run yum. The error leading to this problem was: >> >> /usr/lib/python2.3/site-packages/libxml2mod.so: undefined symbol: >> xmlNewDocPI >> >> Please install a package which provides this module, or >> verify that the module is installed correctly. >> >> It's possible that the above module doesn't match the >> current version of Python, which is: >> 2.3.4 (#1, May 2 2007, 19:26:00) >> [GCC 3.4.6 20060404 (Red Hat 3.4.6-8)] >> -=-=-=-=-=-=- >> >> I have absolutely no clue what might've broken this. I've never had a >> problem using yum on the machine and I've added a few packages to it >> previously without a problem. Anyway to try to fix it I manually >> snagged 'libxml2-python-2.6.16-10.i386.rpm' from the CentOS4 >> repository, which is where libxml2mod.so is provided, etc, etc, etc [snip] > > Oh wait. I didn't break anything. Unlike any other distribution that > I've come across, CentOS just isn't smart enough to know when you run > 'yum' from 'su' that it should still provide access to the same > dependencies. > > Stability is great, but this is the most obtuse distribution of linux > that I've ever had the misfortune to be forced to use. What? How did this get confused, via a LD_LIBRARY_PATH setting perhape? The root user doens't use LD_LIBRARY_PATH, for seurity reasons. |