Bug#765430: ldd: no version information available (required by /lib/x86_64-linux-gnu/libgcrypt.so.20)

[Tim Connors]

On Wed, 15 Oct 2014, Daniel Kahn Gillmor wrote:

> On 10/14/2014 11:17 PM, Tim Connors wrote:
> > Package: libgcrypt20
> > Version: 1.6.2-4
> > Severity: normal
> >
> > Looks like dependencies on libgpg-error not specified correctly?
> >
> > 361711,14> ldd /lib/x86_64-linux-gnu/libgcrypt.so.20
> > /lib/x86_64-linux-gnu/libgcrypt.so.20: /lib/x86_64-linux-gnu/libgpg-error.so.0: no version information available (required by /lib/x86_64-linux-gnu/libgcrypt.so.20)
> >         linux-vdso.so.1 (0x00007fff73dfc000)
> >         libgpg-error.so.0 => /lib/x86_64-linux-gnu/libgpg-error.so.0 (0x00007f328620f000)
> >         libc.so.6 => /lib/x86_64-linux-gnu/libc.so.6 (0x00007f3285e67000)
> >         /lib64/ld-linux-x86-64.so.2 (0x00007f3286719000)
> >
> > This breaks the like of pasuspender:
> >
> > 361712,15> /usr/bin/pasuspender /bin/true
> > /usr/bin/pasuspender: /lib/x86_64-linux-gnu/libgpg-error.so.0: no version information available (required by /lib/x86_64-linux-gnu/libgcrypt.so.20)
>
> fwiw, i don't think this is due to the fact that libgpg-error only
> recently (as of 1.14, i think) adding a GPG_ERROR_1.0 version node in
> its library symbols.
>
> I believe this should just be a warning, and not a hard error, though.
>
> See the discussion with libgpg-error upstream here:
>
>  http://thread.gmane.org/gmane.linux.debian.alioth.pkg-gnupg.general/270

I don't know whether it's a diagnostic, but I just upgraded libgpg-error0
from /stable to /unstable (1.10-3.1 to 1.16-2), and that got rid of the
ldd linker warning.

-- 
Tim Connors