Your message dated Tue, 20 Oct 2026 19:06:18 +0000
with message-id <[email protected]>
and subject line Bug#1141069: fixed in privoxy 4.2.0-2
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-2
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: Tue, 20 Oct 2026 20:22:17 +0200
Source: privoxy
Architecture: source
Version: 4.2.0-2
Distribution: unstable
Urgency: medium
Maintainer: Roland Rosenfeld <[email protected]>
Changed-By: Roland Rosenfeld <[email protected]>
Closes: 1138398 1141069
Changes:
 privoxy (4.2.0-2) unstable; urgency=medium
 .
   [ Luca Boccassi ]
   * Install and use sysusers.d/tmpfiles.d config files.
 .
   [ Roland Rosenfeld ]
   * Small changes on tmpfiles.d fitting the old postinst.
   * 35_openssl4: Add support for OpenSSL 4.x (Closes: #1138398).
   * Update debian/upstream/signing-key.asc subkey.
   * 36_tolerate-flakiness: ignore flaky bad-ssl tests (Closes: #1141069).
   * Upgrade to debhelper 14 (use dh-sequence-single-binary, prefix most
     debian/* files with "privoxy.")
   * salsa-ci.yml: allow_failure for uscan (SorceForge is flaky).
   * Remove undefined ${misc:Pre-Depends}, ${perl:Depends}.
   * debconf-updatepo to fix rename from templates to privoxy.templates.
Checksums-Sha1:
 cedafbb36c1b456dd12b99f2cab7095ac80bbabc 2476 privoxy_4.2.0-2.dsc
 791eac8ee435683e6e47bfb515173001e9c92276 36624 privoxy_4.2.0-2.debian.tar.xz
 cdcbed25c41be5860f7b3c60f03f38a1dd821629 11011 privoxy_4.2.0-2_source.buildinfo
Checksums-Sha256:
 74a789c2b2deecd8645672c44c6f0dbec62fa339dec65becc62e03d16204306f 2476 
privoxy_4.2.0-2.dsc
 06cb03ad1e386087e472dd8d382ec56d8badc950b7e58c3fce49ecbad3096455 36624 
privoxy_4.2.0-2.debian.tar.xz
 58eb0caf48b3dabde3b2569f564290e8e8e282a3d83a2f52bce419269bb9749f 11011 
privoxy_4.2.0-2_source.buildinfo
Files:
 081e7b4a03295e091bdef5e9fd0b558e 2476 web optional privoxy_4.2.0-2.dsc
 5db205a752135176e4d608ec92ad2a9b 36624 web optional 
privoxy_4.2.0-2.debian.tar.xz
 2f1cea398ef6dd46b2087d4c0e6b2aac 11011 web optional 
privoxy_4.2.0-2_source.buildinfo

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

iQIzBAEBCgAdFiEErC+9sQSUPYpEoCEdAnE7z8pUELIFAmrXsXoACgkQAnE7z8pU
ELLrQg//b20hO9cmEiZwTklmUIlI41s5TiGWlUGO/xQsMqO8zqSBFt9HYUlgekzM
WKV2DyXg3mfn1RNglsYnIFbw1qgAvdRRXPStrITWf488+RZkOerhZjE7slrQ644V
AREXyMGsy7lD3kUFyFsq0dbAR866aMDxPKz+laXsxFXCb2MwBHhBM0oDHl1fJJ++
D/winUzRofzDC2InnSTeO/+y+xxD+1D5G86IbIXkFdng6X4qWJI1q4/h2ujCtoxp
r4lNe05kWseoEE9/z70bqjZ3eMQ736uViUYvDcqz80/ASB35MSoNScq4Dr6fUJsR
0DsKA8OndesB7LY8AVJwfBkVzfw6f1VYfUD89TCY0Y/WXsee/nP8j+6/6x6I1+ey
gMMpeUOUPzZIGGzCDKXD/hgzIfzcaUtIX09YAr3S/yN2Hoi7pg6TAx8vMZ2TnSho
H/IAuJZimWQeXBLq3tScyyG2fQaUYMoyWkW/+ahScNSeIqyBVSQqm/SlBO2BSJyJ
+68E0PCBVT9QELHn/FN592XtFLBY9H1NlXe9TZpcLc9GWTHeu8kFybR3pexV10Nl
4U8N6cz55OG+fUaYjs+dTkaBMpZ7Ev4Z+ZdPZiRC5ywigpuHJ1oCfWb5BrOCf3wQ
2R/DTo4tCVRPCXoeXFjoUYKPka/8tsHolNehmllMJaHBzseUtLw=
=XToh
-----END PGP SIGNATURE-----

Attachment: pgpv9xT5bsF_M.pgp
Description: PGP signature


--- End Message ---

Reply via email to