[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]


I'm sure that this is not a dpkg problem, but it is coming up when trying to
use dpkg so I am asking here and hoping someone can point me to where I
should be asking. Im using the current testing distro and when i try to do
an upate I usually encounter the following.

apt-get update
apt-get upgrade
-> scrollkeeper-update: symbol lookup error: /usr/lib/libxslt.so.1:
undefined symbol: xmlXPathContextSetCache

I have had this error a lot in the past and for a lot of different packages.
I get around it by running

apt-get install libxslt1.1
apt-get install libxml2
dpkg --configure -a

I can tell dpkg to install, configure etc, but it would continue to get the
above error until I request the two libraries be installed.

To both of the requests to install libxslt and libxml2, the output states
that they are already the newest version and I see no output to indicate
that they were infact reinstalled. All the files for libxml2 have a modified
date over a month ago, and only the one link for libxslt is modified today.

lrwxrwxrwx 1 root root     17 Dec  4 12:39 /usr/lib/libxslt.so.1 ->

Just to be clear, before trying to update, both the libxml2 and libxslt
libraries were present under /usr/lib. I even checked that the function in
question was linked correctly.

nm -D /usr/lib/libxml2.so | grep xmlXPathContextSetCache
-> 0006b900 T xmlXPathContextSetCache

nm -D /usr/lib/libxslt.so.1 | grep xmlXPathContextSetCache
->         U xmlXPathContextSetCache

and grepped the scrollkeeper-update binary for libxml2.so and libxslt.so
which were both present ( I don't know how to correctly list the dynamic
libraries an executable requires).

So it seems to me, that the only thing that changed by requesting the
libraries be installed was that a link was updated. But even if that were a
broken link, wouldn't I expect the error to complain it couldn't find
functions in libxslt rather than functions in libxml2.

These errors seem to come up every time I try to update, yes I have a
workaround, but I'd like to fix the situation properly.

Any advice would be welcome

View this message in context: http://www.nabble.com/xmlXPathContextSetCache-tf2749203.html#a7670318
Sent from the debian-dpkg mailing list archive at Nabble.com.

Reply to: