Your message dated Thu, 4 Jul 2013 09:20:06 +0200
with message-id
<caljhhg-1+0hdsj-h+caf1tktqtycdyt1rthyv1zw1z63h92...@mail.gmail.com>
and subject line Symlinks in libjson0 moved to /lib/<tripplet>
has caused the Debian Bug report #710676,
regarding libjson0: spurious creation/removal of
/usr/lib/<triplet>/libjson-c.so.2 symlink by ldconfig
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact [email protected]
immediately.)
--
710676: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=710676
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: libjson0
Version: 0.11-1
Severity: important
Hi,
installing libjson0 (the compat layer) causes spurious creation of a
/usr/lib/<triplet>/libjson-c.so.2 symlink by ldconfig. Since libjson0
does not call ldconfig, this will happen at the next call to ldconfig by
another package installation/upgrade - which can happen 2 seconds or 2
months later. So that link shows up spuriously. Same on package removal:
the symlink stays around dangling until ldconfig is called again.
(ldconfig would create /usr/lib/<triplet>/libjson-c.so.2 -> libjson.so.0)
I wanted to prepare patches for this issue as well as for the other
symlink related bugs, but unfortunately the GIT repository is not
up-to-date.
And I wouldn't trust a repository on an anonSCAM host :-)
I think the compat links need to be moved /lib/<triplet>/ since libjson0
was previously moved there for usage e.g. by upstart - putting this to
/usr/lib/*/ will break upstart (with separate /usr fs) until it gets
rebuilt against the new libjson-c2. That will probably fix all the
related bugs. I would also add an explicit call to ldconfig to
libjson0.post{inst,rm} - just to be on a safe side.
Andreas
--- End Message ---
--- Begin Message ---
Version: 0.11-2
This is a fresh unstable chroot with libjson0, libjson-c2, libjson0-dev and
libjson-c-dev installed:
root@howl:/lib/x86_64-linux-gnu# ls -l *json*
lrwxrwxrwx 1 root root 18 Jun 6 18:23 libjson-c.so.2 ->
libjson-c.so.2.0.1
-rw-r--r-- 1 root root 43808 Jun 6 18:23 libjson-c.so.2.0.1
lrwxrwxrwx 1 root root 14 Jun 6 18:23 libjson.so.0 -> libjson-c.so.2
root@howl:/lib/x86_64-linux-gnu# cd /usr/lib/x86_64-linux-gnu/
root@howl:/usr/lib/x86_64-linux-gnu# ls -l *json*
-rw-r--r-- 1 root root 65608 Jun 6 18:23 libjson-c.a
lrwxrwxrwx 1 root root 40 Jun 6 18:23 libjson-c.so ->
/lib/x86_64-linux-gnu/libjson-c.so.2.0.1
lrwxrwxrwx 1 root root 11 Jun 6 18:23 libjson.a -> libjson-c.a
lrwxrwxrwx 1 root root 12 Jun 6 18:23 libjson.so -> libjson-c.so
Andreas, if you have an idea how to get rid of already created symlinks,
please throw it at me :).
O.
--
Ondřej Surý <[email protected]>
--- End Message ---
