On 2016-11-28 16:49:35 [+0200], Adrian Bunk wrote: > Package: polygraph > Version: 4.3.2-4 > Severity: serious > Tags: patch > Control: block 827061 by -1 > > ... > checking for CRYPTO_lock in -lcrypto... no > checking for CRYPTO_add_lock in -lcrypto... no > ... > > Not a perfect solution but an option for stretch is the patch below to > use OpenSSL 1.0.2 > > The "| libssl-dev (<< 1.1.0~)" is added for backports.
could we please keep the bug reporting the way we had it? That means to note that fails to properly build against openssl 1.1 which will remain open with severity important if the package stays with openssl 1.0. > --- debian/control.old 2016-11-28 11:13:51.000000000 +0000 > +++ debian/control 2016-11-28 11:13:57.000000000 +0000 > @@ -6,7 +6,7 @@ > debhelper (>= 9), > dh-autoreconf, > libncurses5-dev, > - libssl-dev, > + libssl1.0-dev | libssl-dev (<< 1.1.0~), > zlib1g-dev, > Standards-Version: 3.9.8 > Homepage: http://www.web-polygraph.org I though we agreed not to tag this as a patch but as a hint what can be done if the maintainer chooses to stay with 1.0. Do you expect this bug to be closed once it switches to libsl1.0-dev? Sebastian
