On 2025-03-13 11:33:05 [+0100], Raphaël Halimi wrote: … > This should also IMHO qualify for the fix to be propagated to stable by a > security update.
So I just got to this again and the current version is newer. Did I fix this or is still outstanding? > Regards, Sebastian
