Bug#760359: libssh2-1-dev: pkgconfig missing dependency on -lgpg-error
Package: libssh2-1-dev Version: 1.4.3-3 Severity: normal Dear Maintainer, /usr/lib/x86_64-linux-gnu/pkgconfig/libssh2.pc has line: Libs.private: -lgcrypt however, libgcrypt depends on libgpg-error, so static linking fails. This should be: Libs.private: -lgcrypt -lgpg-error -- System Information: Debian Release: jessie/sid APT prefers testing APT policy: (500, 'testing') Architecture: amd64 (x86_64) Kernel: Linux 3.14-2-amd64 (SMP w/4 CPU cores) Locale: LANG=ja_JP.UTF-8, LC_CTYPE=ja_JP.UTF-8 (charmap=UTF-8) (ignored: LC_ALL set to ja_JP.UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages libssh2-1-dev depends on: ii libgcrypt20-dev 1.6.1-3 ii libssh2-11.4.3-3 libssh2-1-dev recommends no packages. libssh2-1-dev suggests no packages. -- no debconf information -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#760359: libssh2-1-dev: pkgconfig missing dependency on -lgpg-error
Hi! On Wed, 2014-09-03 at 17:17:11 +0900, Junichi Uekawa wrote: Package: libssh2-1-dev Version: 1.4.3-3 Severity: normal /usr/lib/x86_64-linux-gnu/pkgconfig/libssh2.pc has line: Libs.private: -lgcrypt however, libgcrypt depends on libgpg-error, so static linking fails. This should be: Libs.private: -lgcrypt -lgpg-error While it is true that this will fix the problem, it is fixing it in the wrong place, because it is encoding a possibly internal implementation detail in the depending packages. The proper fix would be to request that libgcrypt gets a pkg-config file so that this information can be encoded where it belongs. Then this pc file could be changed to say: Requires.private: gcrypt or similar. Thanks, Guillem -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#760359: libssh2-1-dev: pkgconfig missing dependency on -lgpg-error
On Thu, Sep 4, 2014 at 3:05 AM, Guillem Jover guil...@debian.org wrote: While it is true that this will fix the problem, it is fixing it in the wrong place, because it is encoding a possibly internal implementation detail in the depending packages. The proper fix would be to request that libgcrypt gets a pkg-config file so that this information can be encoded where it belongs. Then this pc file could be changed to say: Requires.private: gcrypt or similar. I agree and the patch in -4 contains an explanation along the same lines. However for the time being there is no .pc in gcrypt. Junichi: could you please open a bug against gcrypt requesting .pc? Best regards, Mikhail Gusarov. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
