Hmm, I thought that I have fixed this in 0.11-2.
And I am unable to reproduce the bug in current unstable. Ondrej On Thu, Jul 4, 2013 at 8:25 AM, Andreas Beckmann <a...@debian.org> wrote: > On 2013-07-04 03:27, Kurt Roeckx wrote: > > On Wed, Jul 03, 2013 at 05:35:35PM +0200, Ondrej Surı wrote: > >>> fabien boucher <fabien.dot.bouc...@gmail.com> > >>> libjson0-dev : json-c > >>> /usr/lib/x86_64-linux-gnu/libjson.so > >> > >> Also a false positive - this is result of json to json-c library name > >> transition made by upstream and the symlink is kept there to allow > programs > >> to be compiled with -ljson. > > > > I see: > > /usr/lib/i386-linux-gnu/libjson.so -> libjson-c.so > > /usr/lib/i386-linux-gnu/libjson-c.so -> > /lib/i386-linux-gnu/libjson-c.so.2.0.1 > > > > And /lib/i386-linux-gnu/libjson-c.so.2.0.1 exists, so I don't see > > why piuparts is giving a warning here. > > IIRC #710676. One of the links is not shipped but generated by ldconfig. > But a -dev package does not call ldconfig, so this link is created > non-deterministically by another package calling ldconfig ... which may > happen shortly after the installation of libjson-dev - or two months later. > > > Andreas > > > -- > To UNSUBSCRIBE, email to debian-devel-requ...@lists.debian.org > with a subject of "unsubscribe". Trouble? Contact > listmas...@lists.debian.org > Archive: http://lists.debian.org/51d51543.2080...@debian.org > > -- Ondřej Surý <ond...@sury.org>
