[Privoxy-devel] Release date for Privoxy 4.2.0 stable

[Fabian Keil]

Fabian Keil via Privoxy-devel <privoxy-devel at lists.privoxy.org> wrote on 2026-05-20 at 10:08:44:

> Roland Rosenfeld <roland at spinnaker.de> wrote on 2026-05-19 at 21:16:51:
> 
> > On Tue, 19 May 2026, Fabian Keil via Privoxy-devel wrote:
> > 
> > > > > FAIL 4: 'Request from client address from denied network range' HTTP, HTTP GET
> > > > > FAIL 5: 'Request from client address from denied network range' HTTP, HTTP GET
> > 
> > > > Are you maybe not testing with a curl binary based on curl-8_20_0,
> > > > the current recommendation in tests/cts/README?
> > 
> > At least the test output says so:
> > * curl 8.20.0-DEV (x86_64-pc-linux-gnu) 
> > * libcurl/8.20.0-DEV OpenSSL/3.5.6 zlib/1.3.1 brotli/1.1.0 zstd/1.5.7 libidn2/2.3.8 libpsl/0.21.2 nghttp2/1.64.0 OpenLDAP/2.6.10
> > * Protocols: dict file ftp ftps gopher gophers http https imap imaps ipfs ipns ldap ldaps mqtt mqtts pop3 pop3s rtsp smtp smtps telnet tftp ws wss
> > * Features: alt-svc AsynchDNS brotli HSTS HTTP2 HTTPS-proxy IDN IPv6 Largefile libz PSL SSL threadsafe TLS-SRP UnixSockets zstd
> > * Disabled: win32-ca-searchpath, win32-ca-search-safe, override-dns, ssl-sessions
> > 
> > > Never mind, I was able to reproduce the two test failures
> > > on a GNU/Linux system and will look into it.
> > 
> > Great to hear.
> 
> I've reported curl's platform-specific return code upstream yesterday [0]
> and hope to get a response soonish. Hopefully upstream will agree that
> the return code should not depend on the platform.
[...]
> [0]: <https://curl.se/mail/lib-2026-05/0013.html>

Upstream did not respond in time for the release so I've disabled
the tests for now.

Fabian
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 833 bytes
Desc: OpenPGP digital signature
URL: <https://lists.privoxy.org/pipermail/privoxy-devel/attachments/20260531/13919a2f/attachment-0001.bin>