On Wed 21/10/2026 11:18, Lydia Sobot wrote: > On Wed Oct 21, 2026 at 5:14 UTC, Bjorn Ketelaars wrote: > > Diff below updates reaction to 2.6.0, which introduces a HTTP ban > > plugin, which is HTTP middleware. Changes: > > https://framagit.org/ppom/reaction/-/releases/v2.6.0 > Cool, kinda forgot about this one since I'm also working on it for > FreeBSD lol > > > > No new failures from 'make test', and works for me on amd64. The HTTP > > ban plugin is untested by me, and marked alpha by upstream: > > https://reaction.ppom.me/plugins/httpban/ > > > > Couple of crates need to be vendorised. I'm hosting the resulting > > tarball myself. > Why? Also my understanding was that ipset was for Linux only but maybe > I'm missing something
ipset crate was already needed for getting 2.5.1 to build: -MODCARGO_CRATES += ipset 0.9.0 # MIT This is because ipset is part of Cargo.lock, see the relevant Cargo.lock entry: https://framagit.org/ppom/reaction/-/blob/main/Cargo.lock?ref_type=heads&blame=0#L2130-2140 The reason for vendoring it now is that the current version requires a specific branch of the crate which isn't available through crates.io. The same applies to the jrsonnet* crates, for example these Cargo.lock entries: https://framagit.org/ppom/reaction/-/blob/main/Cargo.lock?ref_type=heads&blame=0#L2530-2547 So unless I'm overlooking something, I think the fact that ipset itself targets Linux is separate from why we need to vendor it here. BTW, sysutils/reaction currently has no MAINTAINER. Would you be interested in taking it? If not, I’d be happy to pick it up.
