Bug#895959: libnet-ssleay-perl: FTBFS with openssl 1.1.1

2018-08-29 Thread Damyan Ivanov
-=| Kurt Roeckx, 24.08.2018 18:52:57 +0200 |=- > On Fri, Aug 24, 2018 at 10:27:16AM +, Damyan Ivanov wrote: > > -=| Kurt Roeckx, 23.08.2018 22:32:13 +0200 |=- > > > Note that the SIGPIPE issue is probably a known upstream issue > > > that still needs to be fixed, we're at least still working on

Bug#895959: libnet-ssleay-perl: FTBFS with openssl 1.1.1

2018-08-24 Thread Kurt Roeckx
On Fri, Aug 24, 2018 at 10:27:16AM +, Damyan Ivanov wrote: > -=| Kurt Roeckx, 23.08.2018 22:32:13 +0200 |=- > > Note that the SIGPIPE issue is probably a known upstream issue > > that still needs to be fixed, we're at least still working on a > > SIGPIPE issue. > > > > But that does not mean t

Bug#895959: libnet-ssleay-perl: FTBFS with openssl 1.1.1

2018-08-24 Thread Damyan Ivanov
-=| Kurt Roeckx, 23.08.2018 22:32:13 +0200 |=- > Note that the SIGPIPE issue is probably a known upstream issue > that still needs to be fixed, we're at least still working on a > SIGPIPE issue. > > But that does not mean that the other issues in libnet-ssleay-perl > should not get fixed. I tried

Bug#895959: libnet-ssleay-perl: FTBFS with openssl 1.1.1

2018-08-23 Thread Kurt Roeckx
On Thu, Aug 23, 2018 at 10:32:13PM +0200, Kurt Roeckx wrote: > Note that the SIGPIPE issue is probably a known upstream issue > that still needs to be fixed, we're at least still working on a > SIGPIPE issue. OpenSSL might only be able to handle the EPIPE case, and the applications might need to h

Bug#895959: libnet-ssleay-perl: FTBFS with openssl 1.1.1

2018-08-23 Thread Kurt Roeckx
Note that the SIGPIPE issue is probably a known upstream issue that still needs to be fixed, we're at least still working on a SIGPIPE issue. But that does not mean that the other issues in libnet-ssleay-perl should not get fixed.