From fk at fabiankeil.de Tue Jun 2 11:20:04 2026 From: fk at fabiankeil.de (Fabian Keil) Date: Tue, 2 Jun 2026 11:20:04 +0200 Subject: [Privoxy-devel] Release date for Privoxy 4.2.0 stable In-Reply-To: <20260531213219.39de4e50.fk@fabiankeil.de> References: <20260411094609.628af6a5.fk@fabiankeil.de> <20260502152001.793bbd3b.fk@fabiankeil.de> <20260516072859.17e5c8dc.fk@fabiankeil.de> <20260531125049.16d4c85b.fk@fabiankeil.de> <20260531213219.39de4e50.fk@fabiankeil.de> Message-ID: <20260602112004.5798cb0c.fk@fabiankeil.de> Fabian Keil via Privoxy-devel wrote on 2026-05-31 at 21:32:19: > Fabian Keil via Privoxy-devel wrote on 2026-05-31 at 12:50:49: > > > Fabian Keil via Privoxy-devel wrote on 2026-05-16 at 07:28:59: > > > > > Fabian Keil via Privoxy-devel wrote on 2026-05-02 at 15:20:01: > > > > > > > Fabian Keil via Privoxy-devel wrote on 2026-04-11 at 09:46:09: > > > > > > I also would like the yet-to-be-drafted 4.2.0 announcement > > > > to mention the financial problems the project is having and > > > > announce additional donation options (as proposed on the > > > > team-internal list). This will take a bit more time. > > > > > > > > Delaying the release a couple of weeks should also > > > > allow me to push MbedTLS 4.0 support. > > > > > > That didn't happen (yet), but I received a report of two > > > potential security issues and am currently testing patches. > > > > > > Therefore I propose that we do the release on the weekend > > > starting on 2026-05-30. > > > > I've pushed the patches to git ([0],[1]). > > > > A preliminary announcement is available at [2]. It contains a > > paragraph about the lack of funding but maybe it should also > > mention the fact that there will not be Windows packages at > > the time of the release. > > > > If there are no objections, I'd like to create the tag > > for Privoxy 4.2.0 later today or early tomorrow. > > I've received a response from the reporter so I'll have to > modify the preliminary announcement before sending it out. > > I will therefore not create the v_4_2_0 tag today. > > It could still happen tomorrow, but it probably won't be early ... I've updated the announcement and intend to create the v_4_2_0 tag later today. Fabian -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: application/pgp-signature Size: 833 bytes Desc: OpenPGP digital signature URL: From fk at fabiankeil.de Tue Jun 2 15:28:41 2026 From: fk at fabiankeil.de (Fabian Keil) Date: Tue, 2 Jun 2026 15:28:41 +0200 Subject: [Privoxy-devel] PACKAGERS file still useful? Message-ID: <20260602152841.391da86a.fk@fabiankeil.de> Is anyone actively using the PACKAGERS file [0]? It's not obvious to me that the file is useful so if there are no objections I intend to delete it after the 4.2.0 release instead of trying to update it. Fabian [0]: -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: application/pgp-signature Size: 833 bytes Desc: OpenPGP digital signature URL: From iansilvester at fastmail.fm Tue Jun 2 15:31:39 2026 From: iansilvester at fastmail.fm (Ian Silvester) Date: Tue, 02 Jun 2026 09:31:39 -0400 Subject: [Privoxy-devel] PACKAGERS file still useful? In-Reply-To: <20260602152841.391da86a.fk@fabiankeil.de> References: <20260602152841.391da86a.fk@fabiankeil.de> Message-ID: Fine by me. On Tue, 2 Jun 2026, at 09:28, Fabian Keil via Privoxy-devel wrote: > Is anyone actively using the PACKAGERS file [0]? > > It's not obvious to me that the file is useful so if there > are no objections I intend to delete it after the 4.2.0 release > instead of trying to update it. > > Fabian > > [0]: > > _______________________________________________ > Privoxy-devel mailing list > Privoxy-devel at lists.privoxy.org > https://lists.privoxy.org/mailman/listinfo/privoxy-devel From fk at fabiankeil.de Tue Jun 2 18:02:21 2026 From: fk at fabiankeil.de (Fabian Keil) Date: Tue, 2 Jun 2026 18:02:21 +0200 Subject: [Privoxy-devel] Privoxy 4.2.0 has been tagged (was: Release date for Privoxy 4.2.0 stable) In-Reply-To: <20260602112004.5798cb0c.fk@fabiankeil.de> References: <20260411094609.628af6a5.fk@fabiankeil.de> <20260502152001.793bbd3b.fk@fabiankeil.de> <20260516072859.17e5c8dc.fk@fabiankeil.de> <20260531125049.16d4c85b.fk@fabiankeil.de> <20260531213219.39de4e50.fk@fabiankeil.de> <20260602112004.5798cb0c.fk@fabiankeil.de> Message-ID: <20260602180221.56ee8a2d.fk@fabiankeil.de> Fabian Keil via Privoxy-devel wrote on 2026-06-02 at 11:20:04: > I've updated the announcement and intend to create the v_4_2_0 tag later today. I have created the tag for Privoxy 4.2.0 and have uploaded the source tarball to SF and the website. Fabian -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: application/pgp-signature Size: 833 bytes Desc: OpenPGP digital signature URL: From fk at fabiankeil.de Wed Jun 3 15:03:26 2026 From: fk at fabiankeil.de (Fabian Keil) Date: Wed, 3 Jun 2026 15:03:26 +0200 Subject: [Privoxy-devel] Privoxy 4.2.0 has been tagged In-Reply-To: <20260602180221.56ee8a2d.fk@fabiankeil.de> References: <20260411094609.628af6a5.fk@fabiankeil.de> <20260502152001.793bbd3b.fk@fabiankeil.de> <20260516072859.17e5c8dc.fk@fabiankeil.de> <20260531125049.16d4c85b.fk@fabiankeil.de> <20260531213219.39de4e50.fk@fabiankeil.de> <20260602112004.5798cb0c.fk@fabiankeil.de> <20260602180221.56ee8a2d.fk@fabiankeil.de> Message-ID: <20260603150326.53f93a88.fk@fabiankeil.de> Fabian Keil via Privoxy-devel wrote on 2026-06-02 at 18:02:21: > I have created the tag for Privoxy 4.2.0 and have > uploaded the source tarball to SF and the website. I intend to update the website and send out the announcement later today, maybe in about five hours. Please speak up, if you want me to wait. Fabian -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: application/pgp-signature Size: 833 bytes Desc: OpenPGP digital signature URL: From iansilvester at fastmail.fm Wed Jun 3 15:07:37 2026 From: iansilvester at fastmail.fm (Ian Silvester) Date: Wed, 03 Jun 2026 09:07:37 -0400 Subject: [Privoxy-devel] Privoxy 4.2.0 has been tagged In-Reply-To: <20260603150326.53f93a88.fk@fabiankeil.de> References: <20260411094609.628af6a5.fk@fabiankeil.de> <20260502152001.793bbd3b.fk@fabiankeil.de> <20260516072859.17e5c8dc.fk@fabiankeil.de> <20260531125049.16d4c85b.fk@fabiankeil.de> <20260531213219.39de4e50.fk@fabiankeil.de> <20260602112004.5798cb0c.fk@fabiankeil.de> <20260602180221.56ee8a2d.fk@fabiankeil.de> <20260603150326.53f93a88.fk@fabiankeil.de> Message-ID: I haven't yet run the testsl suite on macOS - I have it planned for the weekend. If you think the likelihood of platform-specific failures is low (it is effectively BSD below the GUI) then go ahead as planned. Ian On Wed, 3 Jun 2026, at 09:03, Fabian Keil via Privoxy-devel wrote: > Fabian Keil via Privoxy-devel wrote > on 2026-06-02 at 18:02:21: > >> I have created the tag for Privoxy 4.2.0 and have >> uploaded the source tarball to SF and the website. > > I intend to update the website and send out the announcement > later today, maybe in about five hours. > > Please speak up, if you want me to wait. > > Fabian > > _______________________________________________ > Privoxy-devel mailing list > Privoxy-devel at lists.privoxy.org > https://lists.privoxy.org/mailman/listinfo/privoxy-devel From fk at fabiankeil.de Wed Jun 3 16:02:33 2026 From: fk at fabiankeil.de (Fabian Keil) Date: Wed, 3 Jun 2026 16:02:33 +0200 Subject: [Privoxy-devel] Privoxy 4.2.0 has been tagged In-Reply-To: References: <20260411094609.628af6a5.fk@fabiankeil.de> <20260502152001.793bbd3b.fk@fabiankeil.de> <20260516072859.17e5c8dc.fk@fabiankeil.de> <20260531125049.16d4c85b.fk@fabiankeil.de> <20260531213219.39de4e50.fk@fabiankeil.de> <20260602112004.5798cb0c.fk@fabiankeil.de> <20260602180221.56ee8a2d.fk@fabiankeil.de> <20260603150326.53f93a88.fk@fabiankeil.de> Message-ID: <20260603160233.5de5dcb2.fk@fabiankeil.de> "Ian Silvester" wrote on 2026-06-03 at 09:07:37: > I haven't yet run the testsl suite on macOS - I have it planned for the weekend. Good to now, thanks for the info. > If you think the likelihood of platform-specific failures is low (it is effectively > BSD below the GUI) then go ahead as planned. While I think there a fair chance that you will run into platform-specific issues when trying to execute the tests below test/cts under macOS, it seems also likely to me that the problems discovered will be tracked down to issues in the test suite as opposed to platform-specific Privoxy bugs. Either way, I'd prefer not to delay the formal release announcement until the weekend. If it turns out that there's a serious macOS-specific bug after all, we can do another release in the near future. Fabian -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: application/pgp-signature Size: 833 bytes Desc: OpenPGP digital signature URL: