libxml2 on CentOS 5.9

user167772 asked:

I’m having problems with a CentOS 5.9 web server running php sites. Apparently libxml2 2.6.26-2.1.21.el5_9.2 has a known bug, but there doesn’t seem like they’ve put the newer release into the repo’s, as you can’t update it using yum.

I searched a lot on this, and also found a few other posts here on Serverfault, but it hasn’t worked. I tried Chad’s solution here but failed at the last stage. When I tried to do the yum localinstall, it gives me this:

Transaction Check Error:
  file /usr/share/man/man1/xmlcatalog.1.gz from install of libxml2-2.7.8-1.x86_64 conflicts with file from package libxml2-2.6.26-2.1.21.el5_9.2.i386
  file /usr/share/man/man1/xmllint.1.gz from install of libxml2-2.7.8-1.x86_64 conflicts with file from package libxml2-2.6.26-2.1.21.el5_9.2.i386
  file /usr/share/man/man1/xmlcatalog.1.gz from install of libxml2-2.7.8-1.x86_64 conflicts with file from package libxml2-2.6.22-1.i386
  file /usr/share/man/man1/xmllint.1.gz from install of libxml2-2.7.8-1.x86_64 conflicts with file from package libxml2-2.6.22-1.i386
  file /usr/share/man/man3/libxml.3.gz from install of libxml2-2.7.8-1.x86_64 conflicts with file from package libxml2-2.6.22-1.i386

So, I thought that perhaps I could --force this, but I don’t want to do it if it might overwrite something that the system needs, and cause more errors down the line.

On the bug report, Daniel Veillard says there is a fix:

“A single upstream commit seems to fix the problem”

That sentence makes no sense to me whatsoever, and the link he posted did not clarify in the slightest.

I would appreciate any help with this. I see that it’s complaining about files from the 32-bit packages, which I find strange since I’m trying to install 64-bit packages. I would think it would leave the 32-bit ones alone.

My answer:


You have both the 32-bit and 64-bit packages on your system now, so in order to update them you must update them both at the same time with the same yum localinstall invocation.


View the full question and answer on Server Fault.

Creative Commons License
This work is licensed under a Creative Commons Attribution-ShareAlike 3.0 Unported License.