Am 21.09.2019 um 12:22 teilte Andrey Rahmatullin mit: > On Sat, Sep 21, 2019 at 12:00:48PM +0200, Hilmar Preuße wrote: Hi, >> in [1] I changed the BD of dvisvgm from ghostscript to libgs-dev (BD on >> gs was removed later on), due to #940700. The package still compiles >> fine, but lintian now moans: >> >> E: dvisvgm: possible-gpl-code-linked-with-openssl >> >> Indeed the new package now depends on libssl1.1 and the binary is linked >> with "libssl1.1:i386: /usr/lib/i386-linux-gnu/libcrypto.so.1.1". Anybody >> having a clue, why this happens? > The package looks for libcrypto and links it if it's available. The > 2.7.3-2 says "checking for LIBCRYPTO... no". > It's not very interesting to find why it's now installed in the build env > (assuming you build it in a clean env), > "assuming you build it in a clean env" --> That was the trick. Works when using pbuilder. Thanks for the reminder! Hilmar -- sigfault #206401 http://counter.li.org
Attachment:
signature.asc
Description: OpenPGP digital signature