[xml/sgml-pkgs] Bug#442292: Bug#442292:

[Justin M. Keyes]

On 9/17/07, Justin M. Keyes <justinkz at gmail.com> wrote:
> On 9/17/07, Mike Hommey <mh at glandium.org> wrote:
> > Try something like strace -eopen -f update-mime-database 2>&1 | grep libz.so
> > and check where libz.so is taken from.
> > If it's not taken in /usr/lib or /lib, then you're likely to have a
> > broken LD_LIBRARY_PATH and/or a spurious libz.so somewhere else.
>
> $ strace -eopen -f update-mime-database 2>&1 | grep libz.so
> open("/usr/local/lib/libz.so.1", O_RDONLY) = 3
>
> [snip]
>
> Should I set the soft link at /usr/local/lib/libz.so.1 to point to
> /usr/lib/libz.so.1.2.3.3 (seems a tenuous solution)?

I tried this. It works long enough to let me update some packages, but
then 'apt-get dist-upgrade' sets it back at some point. Re-setting the
link (again) to point to /usr/lib/libz.so.1.2.3.3 and running apt-get
dist-upgrade multiple times allowed me to get my system up-to-date.
But each time, apt-get seems to set /usr/local/lib/libz.so.1 to point
to /usr/local/lib/libz.so.1.2.3.

Of course, this is orthogonal to the problem, because as I understand
it, programs should be looking in /usr/lib/ to begin with.

-- 
Justin M. Keyes