Source: stunnel4 Version: 3:5.56-1 Severity: serious Justification: FTBFS on amd64 Tags: bullseye sid ftbfs Usertags: ftbfs-20200322 ftbfs-bullseye
Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part (hopefully): > make[1]: Entering directory '/<<PKGBUILDDIR>>' > env TEST_STUNNEL=/<<PKGBUILDDIR>>/src/stunnel debian/tests/runtime > Found the certificate at debian/tests/certs/certificate.pem and the private > key at debian/tests/certs/key.pem > Using the /tmp/p4obeQVBIN temporary directory > About to get the stunnel version information > Got stunnel version 5.56 > Listening for cleartext connections on 127.0.0.1:6502 > Connected to 127.0.0.1:6502, local 127.0.0.1:48160 > Accepted a connection from 127.0.0.1:48160 > Got a local connection id 127.0.0.1:48160 > Waiting for the server to acknowledge a completed client connection > Got an eof from 127.0.0.1:48160, all seems well > Waiting for the client connection itself to report completion > Looks like we are done with the test cleartext connection! > Got listening port 8086 for the stunnel server > Let us hope this was enough to get stunnel to listen there... > Created the stunnel config file /tmp/p4obeQVBIN/stunnel.conf: > ====== > pid = /tmp/p4obeQVBIN/stunnel.pid > foreground = yes > output = /tmp/p4obeQVBIN/stunnel.log > > cert = debian/tests/certs/certificate.pem > key = debian/tests/certs/key.pem > > [test] > accept = 127.0.0.1:8086 > connect = 127.0.0.1:6502 > ====== > 2020.03.22 08:45:58 LOG5[ui]: stunnel 5.56 on x86_64-pc-linux-gnu platform > 2020.03.22 08:45:58 LOG5[ui]: Compiled/running with OpenSSL 1.1.1e 17 Mar > 2020 > 2020.03.22 08:45:58 LOG5[ui]: Threading:PTHREAD Sockets:POLL,IPv6,SYSTEMD > TLS:ENGINE,FIPS,OCSP,PSK,SNI Auth:LIBWRAP > 2020.03.22 08:45:58 LOG5[ui]: Reading configuration from file > /tmp/p4obeQVBIN/stunnel.conf > 2020.03.22 08:45:58 LOG5[ui]: UTF-8 byte order mark not detected > 2020.03.22 08:45:58 LOG5[ui]: FIPS mode disabled > 2020.03.22 08:45:58 LOG4[ui]: Insecure file permissions on > debian/tests/certs/key.pem > 2020.03.22 08:45:58 LOG5[ui]: Configuration successful > 2020.03.22 08:45:59 LOG5[0]: Service [test] accepted connection from > 127.0.0.1:51458 > 2020.03.22 08:45:59 LOG5[0]: s_connect: connected 127.0.0.1:6502 > 2020.03.22 08:45:59 LOG5[0]: Service [test] connected remote server from > 127.0.0.1:48164 > 2020.03.22 08:45:59 LOG3[0]: SSL_read: ../ssl/record/rec_layer_s3.c:302: > error:14095126:SSL routines:ssl3_read_n:unexpected eof while reading > 2020.03.22 08:45:59 LOG5[0]: Connection reset: 18 byte(s) sent to TLS, 0 > byte(s) sent to socket > A fatalerror occurred writing to the 127.0.0.1:48164 connection: Connection > reset by peer > The listener's close message timed out > __DIE__ handler invoked: The listener did not acknowledge the connection > The listener did not acknowledge the connection > Started the stunnel server, pid 22952 > Trying a connection through stunnel, iteration 1 > Trying to connect to the stunnel server at 127.0.0.1:8086 > ...connected! > Registered a client connection as 127.0.0.1:51458 > Waiting for the cleartext listener to receive this connection > Accepted a connection from 127.0.0.1:48164 > Oof, let us see if there are any children left > Pffth, sending a SIGKILL to 22952 > Some children remaining, laying low for a second... > - waiting for 22952 (stunnel server (127.0.0.1:8086)) > - OK, 22952 done > make[1]: *** [debian/rules:33: override_dh_auto_test] Error 10 The full build log is available from: http://qa-logs.debian.net/2020/03/22/stunnel4_5.56-1_unstable.log A list of current common problems and possible solutions is available at http://wiki.debian.org/qa.debian.org/FTBFS . You're welcome to contribute! About the archive rebuild: The rebuild was done on EC2 VM instances from Amazon Web Services, using a clean, minimal and up-to-date chroot. Every failed build was retried once to eliminate random failures.
