Your message dated Wed, 21 Oct 2026 18:34:01 +0000
with message-id <[email protected]>
and subject line Bug#1141069: fixed in privoxy 4.2.0-3
has caused the Debian Bug report #1141069,
regarding privoxy: Use of badssl.com in autopkgtests is flaky
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 [email protected]
immediately.)


-- 
1141069: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1141069
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Source: privoxy
Version: 4.2.0-1
Severity: normal

Dear Maintainer,

The privoxy check-ssl autopkgtest is flaky and unreliable. It utilises
badssl.com which regularly returns 503 or other error instead of the expected
403.

  62s 2026-06-26 09:08:52: Requesting https://expired.badssl.com/
  62s 2026-06-26 09:08:52: Ooops. We expected status code 403, but received: 
503.

This breaks privoxy's autopkgests and (perhaps more importantly) introduces
apparent regressions in other packages.

The Github source for badssl.com[1] makes it clear that baddssl.com is not
suitable for automated CI testing.

Please remove the test, or at least mark it flaky until it can provide the
necessary reliability and coverage.

Thanks.

Mark

[1]  https://github.com/chromium/badssl.com#disclaimer

-- System Information:
Debian Release: forky/sid
Architecture: amd64 (x86_64)

Kernel: Linux 6.19.11+deb14-amd64 (SMP w/2 CPU threads; PREEMPT)
Kernel taint flags: TAINT_CPU_OUT_OF_SPEC, TAINT_WARN
Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8), 
LANGUAGE=en_GB:en
Shell: /bin/sh linked to /usr/bin/dash
Init: OpenRC (via /run/openrc), PID 1: init

--- End Message ---
--- Begin Message ---
Source: privoxy
Source-Version: 4.2.0-3
Done: Roland Rosenfeld <[email protected]>

We believe that the bug you reported is fixed in the latest version of
privoxy, 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 [email protected],
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Roland Rosenfeld <[email protected]> (supplier of updated privoxy 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 [email protected])


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

Format: 1.8
Date: Wed, 21 Oct 2026 20:05:44 +0200
Source: privoxy
Architecture: source
Version: 4.2.0-3
Distribution: unstable
Urgency: medium
Maintainer: Roland Rosenfeld <[email protected]>
Changed-By: Roland Rosenfeld <[email protected]>
Closes: 1141069
Changes:
 privoxy (4.2.0-3) unstable; urgency=medium
 .
   * Now really ignore flaky bad-ssl tests (Closes: #1141069).
Checksums-Sha1:
 3f6c98682f8af369f1f700732e6e82470d20737d 2476 privoxy_4.2.0-3.dsc
 2e7fdc063637c7d482d85a044e9f5127c9ae1220 36688 privoxy_4.2.0-3.debian.tar.xz
 b84f01144a34ed96a81fa05531c117bde1e8358b 11011 privoxy_4.2.0-3_source.buildinfo
Checksums-Sha256:
 aebc6588739dde1ecf1b5222d660904c3a45f8f8d949455a6521a645deaa2670 2476 
privoxy_4.2.0-3.dsc
 fddafe615594f6b9eb4d19e8e32f0b95c44245242859d492c3b7993670c415af 36688 
privoxy_4.2.0-3.debian.tar.xz
 81d306263eb068f6d68358ef5767ff715ab838c25d8c4fc5dafe299efb7c3fe5 11011 
privoxy_4.2.0-3_source.buildinfo
Files:
 3742d2bb06069fd72fb46a8e163dafa0 2476 web optional privoxy_4.2.0-3.dsc
 996fcef6e9aaf9f95664f61e2f1e769e 36688 web optional 
privoxy_4.2.0-3.debian.tar.xz
 44812fd4c7e5000f14d271881c7fbd87 11011 web optional 
privoxy_4.2.0-3_source.buildinfo

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

iQIzBAEBCgAdFiEErC+9sQSUPYpEoCEdAnE7z8pUELIFAmrY/xgACgkQAnE7z8pU
ELIEMQ/+KKipfm73kdU08q3TC/vw8iGyS6E5l9QBii6Sk6aUqt6MY27cuO9dqD9d
h6cUL4Pai6z6PKQtb0B/V2iOPz9KMpc2vwgR2zX/v2xtumWeZH2TV/11jeNAL53I
Qitgf3RuMRBsYM1sYJRZWc6Sp4OpE9fP7LtxHZrX5YaDaaekX7PkRntVITTahSKX
8tv6j8AxMW+/pkfpQWJQhU0KeHI2UB0yQUn9KU03ZFIZ6FwFsNfEIbWFmcZsTQJm
d3iR3cvEkgZ3OSDOdFwhgv/TT1yaFcvFLUdoaSCetxmyU8L8s/8zNUJB72sv3PuJ
yqmqOdy5xOEhHSqzBA1aP0QWX85HULoHvpqk8xGk0nxP0yP6t+zc6zpH/AHgGA0T
9XLFohV172UNenglvAHmVLDFkH0ao2hSjnOJwuK9r773uKZIXc5m6MtquhI/ytWT
7SYU/GFnaWds0bLJ2JpZqXKpWz3SUeyGx/R0C5RjfSeCEFRKMruIMnVu6gif1DHy
pVHOR5fOBvkpzz2ed3n7UpIyqGelQDiFNWRkVFChCyzJMBO1tiCiPT83+cEJ941P
0MfsAi8eawpQ0iiwrfeRlp1TQbIKmLkYhgXFLO452dq0tinQg7jz+FQhWiI6KYiG
2U9MMdx5v3+4UnNpr1mm7aVDt1lOXMSoqrcKhXl+yTWRQxFGrbs=
=px5+
-----END PGP SIGNATURE-----

Attachment: pgpSme5drGRr7.pgp
Description: PGP signature


--- End Message ---

Reply via email to