Your message dated Sat, 02 May 2020 11:18:50 +0000
with message-id <e1juqau-000bax...@fasolo.debian.org>
and subject line Bug#954691: fixed in stunnel4 3:5.56+dfsg-1
has caused the Debian Bug report #954691,
regarding stunnel4: FTBFS: A fatalerror occurred writing to the 127.0.0.1:48164 
connection: Connection reset by peer
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
954691: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=954691
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
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.

--- End Message ---
--- Begin Message ---
Source: stunnel4
Source-Version: 3:5.56+dfsg-1
Done: Peter Pentchev <r...@debian.org>

We believe that the bug you reported is fixed in the latest version of
stunnel4, which is due to be installed in the Debian FTP archive.

A summary of the changes between this version and the previous one is
attached.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to 954...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Peter Pentchev <r...@debian.org> (supplier of updated stunnel4 package)

(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmas...@ftp-master.debian.org)


-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA512

Format: 1.8
Date: Sat, 02 May 2020 14:01:17 +0300
Source: stunnel4
Architecture: source
Version: 3:5.56+dfsg-1
Distribution: unstable
Urgency: medium
Maintainer: Peter Pentchev <r...@debian.org>
Changed-By: Peter Pentchev <r...@debian.org>
Closes: 949779 954691 955710
Changes:
 stunnel4 (3:5.56+dfsg-1) unstable; urgency=medium
 .
   * Make the "runtime" test a bit more robust.
     Closes: #955710, #954691
   * Declare compliance with Debian Policy 4.5.0 with no changes.
   * Add the year 2020 to my debian/* copyright notice.
   * Drop the adequate autopkgtest.
   * Drop the "Name" and "Contact" upstream metadata fields.
   * Update to debhelper compat level 13:
     - drop the conditional around the testing target
     - use "execute_before.." and "execute_after..." targets
   * Add the 06-hup-separate patch.  Closes: #949779
   * Repack the upstream source, excluding the prebuilt libraries in
     the Windows installer plugins.
Checksums-Sha1:
 1da8c127f5fa07151a9d514dbf327beccc8a06e3 2655 stunnel4_5.56+dfsg-1.dsc
 faa7add2b905683ae5c0938d9044eb0296ab7755 624388 stunnel4_5.56+dfsg.orig.tar.xz
 a026240cb27ea22f3af789cc3f66db607dfa2d0f 833 stunnel4_5.56+dfsg.orig.tar.xz.asc
 0c7b2fe52785df8833dac42bbb3209a3e6391737 47384 
stunnel4_5.56+dfsg-1.debian.tar.xz
Checksums-Sha256:
 96d24c6986e76b9018297cd93293e950f95cca848fb9259bfe92aaa016a7354e 2655 
stunnel4_5.56+dfsg-1.dsc
 93efdc85874b6edd829b99f579b54770dd20854a46e18686704fcf531799e01f 624388 
stunnel4_5.56+dfsg.orig.tar.xz
 b259f1576b90765f123867ce5ba202e439dc1ff259dad3f7d7fe5ee33467cddf 833 
stunnel4_5.56+dfsg.orig.tar.xz.asc
 f4b3a5508575d93744252eb71c614d2b91329c7dbd0d25109bc8f1058488280d 47384 
stunnel4_5.56+dfsg-1.debian.tar.xz
Files:
 c25c8ee218d14cf66c6adb675a11d1d6 2655 net optional stunnel4_5.56+dfsg-1.dsc
 611e27f691c4e67989a766dfae7f6668 624388 net optional 
stunnel4_5.56+dfsg.orig.tar.xz
 9c63d8479fab496a1dc3e90af35d55fc 833 net optional 
stunnel4_5.56+dfsg.orig.tar.xz.asc
 a2d25de8d690512ebcae0cda63ee8a6f 47384 net optional 
stunnel4_5.56+dfsg-1.debian.tar.xz

-----BEGIN PGP SIGNATURE-----

iQJEBAEBCgAuFiEELuenpRf8EkzxFcNUZR7vsCUn3xMFAl6tU7IQHHJvYW1AZGVi
aWFuLm9yZwAKCRBlHu+wJSffEzx0EACdGs5nMyF3ok8nVP60Yk1KivTFIkvpDuff
lxmtdgzY2LU7WGJwk7U8clg+dY4KVvlJSaJvXPSe7+lgDlzomZSsZkCWZajhOcc5
kp+Ean8E44aVFWBqYZqi8QBcMYGzoAt/J9s0g2AbreUp7c+RNXo96LUJYcM/sDpv
sJeNzVh4z025WhMz4fveAHkZuQcwuBfIUaEdFh4AyaySXzOBZQUM1whttZ+zyJ8z
fcQjBUT80Ms2et4n76PemR+Q/9JUFWcm+9HWNP9rYXqVHZU5DuvaluUQApJF8sFK
iRA42BYlFMdKOz6UY5pay94VR+8/HCeVSvWKhe8lGGtuQm1/JXxCfwGBkMKO4WD0
zYN4YVxMqp//ZsnQjRRarmeASlTfn1pu2sJnuC8Bfsk4F6aKz8YNK4N+cQrKgybP
bZGtioWwRxtDRlF3uQE7OsUGbsKdRbPf8xxPE4cgAcU/RRiAuac4LA+t5EQykdDt
crUlJXgOhHEtYCWamQZfGE9xVXsa9RChSAHZWjn31y8azqwc/dmY/4mrgprJikJg
kGcSYICQZUN9yCS8rDn/PBFKhoH+pQAuFqcXBKLTehfKRs//J7kHE5bEbFkafd14
Eh3jfBpI/inFHBX07Asqz7/el7AfDixb/R28OsYoZC20/2HaQXhWAwXzRfeEKdKG
a27kGIeiww==
=dGBW
-----END PGP SIGNATURE-----

--- End Message ---

Reply via email to