[Privoxy-devel] Test failures delaying the 4.0.0 release (was: Releasing 3.0.35 or 4.0?)
Fabian Keil
fk at fabiankeil.de
Sun Jan 12 17:09:40 CET 2025
Roland Rosenfeld <roland at spinnaker.de> wrote on 2025-01-12 at 13:03:41:
> On Sun, 12 Jan 2025, Roland Rosenfeld wrote:
>
> > commit a8f52ce225cc31a5d61f7a8de5da8c7c64834a50
> > Author: Chris Paulson-Ellis <chris.paulson-ellis at motorolasolutions.com>
> > Date: Fri Aug 19 18:58:40 2022 +0100
> >
> > configure: fix broken m4 syntax in TLS options
Great find.
> Instead of applying only this patch, I now tried to use a more recent
> version than "before-cts-regressions" 073268a6de3 and started with
> curl-7_85_0.
> This looks good and worked except test 389.
> So maybe it would be a workaround for the autoconf issue to jump from
> 073268a6de3 to curl-7_85_0 and whitelist 389 as an expected problem.
I've updated the README to use curl-7_85_0.
On my system acl-destination-denied is now the only failing scenario.
> I'm currently running "make test" on curl (without privoxy) to check,
> whether test389 works as expected (I don't understand why
> curlmachine.locahost should ever work).
On my systems hostnames ending in .localhost resolve to 127.0.0.1 and ::1.
fk at t520 ~ $host blafsel.localhost
blafsel.localhost has address 127.0.0.1
blafsel.localhost has IPv6 address ::1
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/20250112/c7045c64/attachment.bin>
More information about the Privoxy-devel
mailing list