From fk at fabiankeil.de Sat Jan 3 14:28:29 2026 From: fk at fabiankeil.de (Fabian Keil) Date: Sat, 3 Jan 2026 14:28:29 +0100 Subject: [Privoxy-devel] Release date for Privoxy 4.1.0 stable In-Reply-To: References: <20251204123308.70b9bc35.fk@fabiankeil.de> <20251206182648.073ba619.fk@fabiankeil.de> Message-ID: <20260103142829.5fa7c40d.fk@fabiankeil.de> Lee wrote on 2025-12-07 at 15:20:37: > On Sat, Dec 6, 2025 at 12:26?PM Fabian Keil via Privoxy-devel wrote: > > > > Lee wrote on 2025-12-06 at 10:54:37: > > > > > On Thu, Dec 4, 2025 at 6:35?AM Fabian Keil via Privoxy-devel > > > It would be nice if someone with a Windows 11 machine would build > > > Privoxy for Windows. > > > > In my opinion it would be even nicer if someone would cross-build > > Privoxy for Windows on a free operating system in a reproducible > > fashion. > > If someone else was doing the cross-build, maybe.. > You'd still need someone with a windows 11 machine to test the new > build of privoxy. Which isn't all that bad, but whoever is doing the > cross-build would also have to cross-build all the libraries - which > is a pain. For whatever reason the brotli 1.2.0 library now requires > 'cmake -DBUILD_SHARED_LIBS=off' and I'm not at all clear about the > zstd documentation talking about "by default the dynamic library is > multithreaded and static library is single-threaded." Is that going > to be a problem for privoxy? I dunno, but at least privoxy hasn't > blown up yet. My understanding is that a zstd library that has been built with multi-threading support can be used to compress in parallel using multiple threads. As Privoxy currently only uses zstd for decompression it shouldn't make a difference. BTW, I intend to tag Privoxy 4.1.0 tomorrow, slightly behind schedule. 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 Sun Jan 4 18:52:28 2026 From: fk at fabiankeil.de (Fabian Keil) Date: Sun, 4 Jan 2026 18:52:28 +0100 Subject: [Privoxy-devel] Privoxy 4.1.0 has been tagged (was: Release date for Privoxy 4.1.0 stable) In-Reply-To: <20260103142829.5fa7c40d.fk@fabiankeil.de> References: <20251204123308.70b9bc35.fk@fabiankeil.de> <20251206182648.073ba619.fk@fabiankeil.de> <20260103142829.5fa7c40d.fk@fabiankeil.de> Message-ID: <20260104185228.03b8a7bb.fk@fabiankeil.de> Fabian Keil via Privoxy-devel wrote on 2026-01-03 at 14:28:29: > BTW, I intend to tag Privoxy 4.1.0 tomorrow, slightly behind schedule. Privoxy 4.1.0 has been tagged and I 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 Tue Jan 13 11:57:59 2026 From: fk at fabiankeil.de (Fabian Keil) Date: Tue, 13 Jan 2026 11:57:59 +0100 Subject: [Privoxy-devel] macOS package changes (was: Privoxy 4.1.0 has been tagged) In-Reply-To: <20260104185228.03b8a7bb.fk@fabiankeil.de> References: <20251204123308.70b9bc35.fk@fabiankeil.de> <20251206182648.073ba619.fk@fabiankeil.de> <20260103142829.5fa7c40d.fk@fabiankeil.de> <20260104185228.03b8a7bb.fk@fabiankeil.de> Message-ID: <20260113115759.5a269ef1.fk@fabiankeil.de> Fabian Keil via Privoxy-devel wrote on 2026-01-04 at 18:52:28: > Fabian Keil via Privoxy-devel wrote on 2026-01-03 at 14:28:29: > > > BTW, I intend to tag Privoxy 4.1.0 tomorrow, slightly behind schedule. > > Privoxy 4.1.0 has been tagged and I have uploaded > the source tarball to SF and the website. Hi Ian, I noticed yesterday that a macOS package was available at SourceForge and copied the files over to the website and onion site mirrors. However, I forgot to regenerate the RSS feed and when I did that today I realised that the package file had been changed in place. Unfortunately the SourceForge feed [0] doesn't seem to mention this change. Both files have valid signatures from the same RSA key (54021FA8034C73730BF0EB74ADE1B21709E73DAF) and I'm optimistically assuming that's yours. I ran the files through diffoscope and came to the conclusion that a major difference is that the more recent package has zstd support. Is that correct? I pulled master from the OSXPackageBuilder and got a new commit [1] that also mentions zstd support. The previous commit [2] is from 2023, though. Do you have a local branch that matches the OSXPackageBuilder state used for the 4.0.0 macOS package and the previous 4.1.0 macOS package? If yes, please push those changes as well. By the way, I also noticed that pushes to the OSXPackageBuilder didn't result in mails to the privoxy-commits@ list [3]. That should be fixed now. Fabian [0]: [1]: [2]: [3]: -------------- 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 Jan 13 13:16:44 2026 From: iansilvester at fastmail.fm (Ian Silvester) Date: Tue, 13 Jan 2026 07:16:44 -0500 Subject: [Privoxy-devel] macOS package changes (was: Privoxy 4.1.0 has been tagged) In-Reply-To: <20260113115759.5a269ef1.fk@fabiankeil.de> References: <20251204123308.70b9bc35.fk@fabiankeil.de> <20251206182648.073ba619.fk@fabiankeil.de> <20260103142829.5fa7c40d.fk@fabiankeil.de> <20260104185228.03b8a7bb.fk@fabiankeil.de> <20260113115759.5a269ef1.fk@fabiankeil.de> Message-ID: Well-spotted Fabian! Yes both versions are from me. In working through the build on Sunday I noticed that there was a far more recent pcre2 available than installed on my (now rather aged) build machine, and in my focus on upgrading that entirely forgot to download and build zstd! I realised overnight so corrected that yesterday and made appropriate tweaks to the macOS build script to include it. I'm afraid though that I don't have local branches representing the prior 4.1.0 nor 4.0.0 states - the package is fairly quiescent these days so I work on the head I'm afraid. Ian On Tue, 13 Jan 2026, at 05:57, Fabian Keil via Privoxy-devel wrote: > Fabian Keil via Privoxy-devel wrote > on 2026-01-04 at 18:52:28: > >> Fabian Keil via Privoxy-devel wrote on 2026-01-03 at 14:28:29: >> >> > BTW, I intend to tag Privoxy 4.1.0 tomorrow, slightly behind schedule. >> >> Privoxy 4.1.0 has been tagged and I have uploaded >> the source tarball to SF and the website. > > Hi Ian, > > I noticed yesterday that a macOS package was available > at SourceForge and copied the files over to the website > and onion site mirrors. > > However, I forgot to regenerate the RSS feed and when I > did that today I realised that the package file had been > changed in place. Unfortunately the SourceForge feed [0] > doesn't seem to mention this change. > > Both files have valid signatures from the same RSA key > (54021FA8034C73730BF0EB74ADE1B21709E73DAF) and I'm optimistically > assuming that's yours. > > I ran the files through diffoscope and came to the conclusion > that a major difference is that the more recent package has > zstd support. Is that correct? > > I pulled master from the OSXPackageBuilder and got a new > commit [1] that also mentions zstd support. The previous > commit [2] is from 2023, though. > > Do you have a local branch that matches the OSXPackageBuilder > state used for the 4.0.0 macOS package and the previous 4.1.0 > macOS package? If yes, please push those changes as well. > > By the way, I also noticed that pushes to the OSXPackageBuilder > didn't result in mails to the privoxy-commits@ list [3]. > That should be fixed now. > > Fabian > > [0]: > [1]: > > [2]: > > [3]: > > _______________________________________________ > Privoxy-devel mailing list > Privoxy-devel at lists.privoxy.org > https://lists.privoxy.org/mailman/listinfo/privoxy-devel From fk at fabiankeil.de Sat Jan 17 14:24:17 2026 From: fk at fabiankeil.de (Fabian Keil) Date: Sat, 17 Jan 2026 14:24:17 +0100 Subject: [Privoxy-devel] macOS package changes In-Reply-To: References: <20251204123308.70b9bc35.fk@fabiankeil.de> <20251206182648.073ba619.fk@fabiankeil.de> <20260103142829.5fa7c40d.fk@fabiankeil.de> <20260104185228.03b8a7bb.fk@fabiankeil.de> <20260113115759.5a269ef1.fk@fabiankeil.de> Message-ID: <20260117142417.20fa4b1a.fk@fabiankeil.de> "Ian Silvester" wrote on 2026-01-13 at 07:16:44: > Yes both versions are from me. In working through the build on > Sunday I noticed that there was a far more recent pcre2 available > than installed on my (now rather aged) build machine, and in my > focus on upgrading that entirely forgot to download and build zstd! > I realised overnight so corrected that yesterday and made appropriate > tweaks to the macOS build script to include it. Thanks for the explanation. > I'm afraid though that I don't have local branches representing the > prior 4.1.0 nor 4.0.0 states - the package is fairly quiescent these > days so I work on the head I'm afraid. In the future, please always push the state used to create published packages to the OSXPackageBuilder repository to improve our GPL compliance. Fabian -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: application/pgp-signature Size: 833 bytes Desc: OpenPGP digital signature URL: