On Wed, Feb 11, 2026 at 07:11:24PM +0100, Alejandro Colomar via Mutt-dev wrote: > On 2026-02-11T18:21:12+0100, Rene Kita wrote: > > Inspired by commit 8b10799c (Fix iswblank() compilation error when > > configured --without-wc-funcs., 2026-01-26) I decided to take a look at > > the CI builds run on sr.ht. [...] > > Some thoughts: > > - I don't think having a built run on Debian Stable is really > > meaningful. Debian stable is most of the time quite old and only > > selected patches will be backported. I would suggest to pick something > > more bleeding edge like Arch. > > Building on a stable system is also useful. Otherwise, you may write > code that works on new systems, but fails on ond ones. I personally use > Devuan unstable on my computer, and having an oldstable CI to test old > systems has caught a few things that I wouldn't have caught on my > computer.
Just to clarify, that argument has to be seen in the context of my remark below about sr.ht only allowing four build manifests that will be submitted on each push. With my upstream maintainer hat on I would put the focus more on the next release than on some oldstable version. [...] > > - sr.ht only allows four build manifests to run for each push. If more > > than four are present a random pick will run. I don't like this idea, > > because it makes the CI somewhat non-deterministic.
