Your message dated Mon, 21 May 2018 17:20:11 +0000
with message-id <e1fkotj-000axs...@fasolo.debian.org>
and subject line Bug#899130: fixed in stunnel4 3:5.44-2
has caused the Debian Bug report #899130,
regarding stunnel4: FTBFS: tests failing returned exit code 2
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.)
--
899130: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=899130
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: stunnel4
Version: 3:5.44-1
Severity: serious
Justification: FTBFS
User: debian-p...@lists.debian.org
Usertags: hh2018
When testing packages against the upcoming release of perl, we found
an unrelated FTBFS on a clean sid chroot:
./make_test
Sat May 19 16:06:30 UTC 2018
stunnel 5.44 on x86_64-pc-linux-gnu platform
Compiled/running with OpenSSL 1.1.0h 27 Mar 2018
Threading:PTHREAD Sockets:POLL,IPv6,SYSTEMD TLS:ENGINE,FIPS,OCSP,PSK,SNI
Auth:LIBWRAP
test 010_require_cert configuration failed
error logs logs/010_require_cert.log
test 011_verify_peer configuration failed
error logs logs/011_verify_peer.log
test 012_verify_chain configuration failed
error logs logs/012_verify_chain.log
test 013_CRL_file configuration failed
error logs logs/013_CRL_file.log
test 014_PSK_secrets configuration failed
error logs logs/014_PSK_secrets.log
test 015_p12_cert configuration failed
error logs logs/015_p12_cert.log
/<<PKGBUILDDIR>>/tests/recipes/020_IPv6: 24:
/<<PKGBUILDDIR>>/tests/recipes/020_IPv6: ifconfig: not found
test 020_IPv6 skipped
test 021_FIPS skipped
test 030_simple_execute configuration failed
error logs logs/030_simple_execute.log
test 031_redirect configuration failed
error logs logs/031_redirect.log
test 032_no_redirect configuration failed
error logs logs/032_no_redirect.log
test 033_redirect_exec configuration failed
error logs logs/033_redirect_exec.log
test 034_no_redirect_exec configuration failed
error logs logs/034_no_redirect_exec.log
test 035_SNI configuration failed
error logs logs/035_SNI.log
test 036_no_SNI configuration failed
error logs logs/036_no_SNI.log
test 037_failover_prio1 configuration failed
error logs logs/037_failover_prio1.log
test 038_failover_prio2 configuration failed
error logs logs/038_failover_prio2.log
test 039_failover_rr configuration failed
error logs logs/039_failover_rr.log
HTTP/1.1 400 Unknown Version
Content-Type: text/html;charset=iso-8859-1
Content-Length: 58
Connection: close
Server: Jetty(9.4.z-SNAPSHOT)
<h1>Bad Message 400</h1><pre>reason: Unknown Version</pre>test 040_reload
failed
error logs logs/040_reload.log
test 110_failure_require_cert ok
test 111_failure_verify_peer ok
test 112_failure_verify_chain ok
test 113_failure_CRL_file ok
test 114_failure_PSK_secrets ok
test 120_failure_no_cert ok
test 121_failure_wrong_config ok
summary: success 7, skip 2, fail 17
./make_test finished
make[3]: *** [Makefile:447: check-local] Error 1
--- End Message ---
--- Begin Message ---
Source: stunnel4
Source-Version: 3:5.44-2
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 899...@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: SHA256
Format: 1.8
Date: Mon, 21 May 2018 18:23:00 +0300
Source: stunnel4
Binary: stunnel4
Architecture: source amd64
Version: 3:5.44-2
Distribution: unstable
Urgency: medium
Maintainer: Peter Pentchev <r...@debian.org>
Changed-By: Peter Pentchev <r...@debian.org>
Description:
stunnel4 - Universal SSL tunnel for network daemons
Closes: 782030 895954 899130
Changes:
stunnel4 (3:5.44-2) unstable; urgency=medium
.
* Declare compliance with Debian Policy 4.1.4 with no changes.
* Add procps to the build dependencies for the upstream test suite.
* Bump the debhelper compat level to 11 with no changes.
* Bump the year on my debian/* copyright notice.
* Change the way the service handles the lack of default configuration:
- drop the ENABLED option from /etc/defaults/stunnel4
- let debhelper take care of not starting the service immediately
after installation (when there are no valid config files yet)
- add a NEWS blurb pointing out how to disable the service if it
is indeed meant to only be started on demand
* Let the init script actually wait for the old stunnel instances to
stop before starting the new ones or even reporting that the old
ones are dead. Closes: #782030
* Use my Debian e-mail address.
* Point the Vcs-* URLs to salsa.debian.org.
* Temporarily drop two tests that rely on an expired certificate and
an expired CRL. Closes: #895954, #899130
* Drop an empty line at the end of the Debian changelog file.
* Drop the "CAs" spelling error override, since recent versions of
Lintian do not consider it an error any more.
* Add a trivial autopkgtest running adequate on the installed package.
Checksums-Sha1:
5efd29fd639c54d718c20f38fb4b6e610481b354 2342 stunnel4_5.44-2.dsc
498b9ef0b5ebdda929aef49a92d1d15aefc2bb02 46740 stunnel4_5.44-2.debian.tar.xz
8600f56f4699aa11084dfa616ca68a5933348e9d 208968
stunnel4-dbgsym_5.44-2_amd64.deb
e390044450dca90178f1af400a5f532f12b6fd6c 6969 stunnel4_5.44-2_amd64.buildinfo
480b52093d2570c2dfc4179f0036ea36aa4f623e 192848 stunnel4_5.44-2_amd64.deb
Checksums-Sha256:
4788cf55d14bf771db46cb6a0789908e0b618aea189fb93496943dfd61b57caf 2342
stunnel4_5.44-2.dsc
686c57ebe6a419f478eb1e81501fcde0c57b12b50624397b98c64fc6173cdd2d 46740
stunnel4_5.44-2.debian.tar.xz
9ccc82f3a7480a35667dece3e3b8f316586110572c10f959bc41b7fef16653ff 208968
stunnel4-dbgsym_5.44-2_amd64.deb
7a24549a8974ee610f6e40ec66bd220c6c8641d1b34dc993851c866774ca701a 6969
stunnel4_5.44-2_amd64.buildinfo
7346686732258ff951e0b7d9e79d4fc65988bf2a6804fbb6c764499b8a299fd9 192848
stunnel4_5.44-2_amd64.deb
Files:
b0e0b59928c2cccddebc4267816fbf44 2342 net optional stunnel4_5.44-2.dsc
9aabf1ebc4a4645c8a4ec878090b41e9 46740 net optional
stunnel4_5.44-2.debian.tar.xz
ed2b7c446617dcbe84c5d68cdc903fbf 208968 debug optional
stunnel4-dbgsym_5.44-2_amd64.deb
ae32c599b7f0de7baa43e7e4c3681888 6969 net optional
stunnel4_5.44-2_amd64.buildinfo
aad64210dc3dd66e25f36758b3b62c16 192848 net optional stunnel4_5.44-2_amd64.deb
-----BEGIN PGP SIGNATURE-----
iQIzBAEBCAAdFiEEfYh9yLp7u6e4NeO63OMQ54ZMyL8FAlsC/HwACgkQ3OMQ54ZM
yL9ClBAAlKFLDEWls/39d3Vfw3CxBQpPJlHXsjB4ZrSmX9DHfG5dnuOqLOT1X3gs
R1pqgAsAb+T96eBP194yGyxW/qXaaE9PP7N8T7F2RjXmkS9WP9r6mV0kqnJ5VgLN
4SqQnAF6VHAsmR1VcXsX+dGI3ERxZBn+EYdLI5De6WYb3ORSrS9kMXMNidUdCsYM
rTJxscTm3i4mk2PaTj/RpRuJSqykBi9+BuWKRkeWtSyZuwQD+Toz+VqsUoitnSlQ
UGaJWNOOk/7QtutV2WJeYSk8M28rBHoVQtbsxu6rA2UMDil3n42MAkdzuUKctqNy
Bkg41y20XpwK0zdwUKTxkwzR+fpoM6TKU0yrh9lQ7z5be1e5yGSq0aDcq85Mibeh
tZYLOoUiAj5Ur3w1Ardaw4UnIyV1jxzVw+WP8vo43QIj5X0iazhpYjzym8wFvZEn
fF6m05MHyhpuaj+RV9Czx+9A/l6cQHcrZEUSRRRVj+GdvDZkdnVyXI4w6msQsj8t
41qNkYJqi5b8th4ygKc6KNldew/Ht3Wcrez6U6pnMDFxtGPuziq+sB4HtpADS5m0
Yw0v7OvAhH0b7ewSog9LhLOb3UrgZvaFtyGnW/tcxnoERfJNA20cerFKx9f+GZWf
nqcm7Vb7n6eilh0EOVJqMyLMS0Cd148Few3kcYn5rA4A9YjWyZw=
=VVgG
-----END PGP SIGNATURE-----
--- End Message ---
