On Sat, 2026-07-25 at 23:11 +0000, Maximiliano Curia wrote: > I think this is already fixed, I couldn't reproduce the issue > building > the current git version, but I think it was fixed in the -2 revision. >
I wasn't sure either it looked like it was working now, but I was waiting for it to get through the builders and CI to see what happened.
