Control: severity -1 normal
Control: reassign -1 src:libsdl-perl,src:sdl12-compat
Control: found -1 libsdl-perl/2.548-6
Control: found -1 sdl12-compat/1.2.74-1
On Mon, 09 Feb 2026 at 18:56:29 +0000, Simon McVittie wrote:
A workaround is possible: we could temporarily revert the sdl12-compat
change, which is necessary when using sdl2-compat as default but we're
not doing that yet in any case.
I've now done this in sdl12-compat (to be uploaded shortly).
I'm downgrading this to non-RC rather than closing it fully, as a
reminder that upstream is still looking into whose bug this is. If it
isn't resolved upstream somehow, we'll likely need some coordination
around this when switching from "classic" SDL 2 to sdl2-compat (at which
point we'd presumably want to reinstate the upstream change that was
causing this test failure, which does resolve a genuine bug, and
accompany that by giving sdl12-compat a versioned B-D on libsdl2-dev to
avoid the failing scenario where you have the new sdl12-compat with the
old SDL).
Using the FTBFS bug report for this purpose rather than the one I opened
for the autopkgtest regression, because that has the necessary tags to
show up on lists of FTBFS bugs and avoid duplicates being opened if
something goes wrong.
smcv
