On Sat, May 02, 2026 at 10:49:55AM +0100, Simon McVittie wrote:
On Sat, 02 May 2026 at 10:36:20 +0100, Simon McVittie wrote:
On Fri, 01 May 2026 at 23:14:09 +0000, Santiago Vila wrote:
self.assertTrue(blit_surf.get_flags() & pygame.RLEACCEL)
This might be an expectations mismatch between pygame and sdl2-compat
Possibly related:
https://github.com/libsdl-org/sdl2-compat/issues/575
Ah, this does look like that issue. The conclusion over there was that
this is a pygame(-ce) test bug rather than a sdl2-compat bug, and in
the pygame-ce fork it was fixed as part of
https://github.com/pygame-community/pygame-ce/pull/3687 (disabling the
failing assertion on sdl2-compat).
The original pygame doesn't seem to be keeping up well with changes to
this sort of implementation detail in SDL2, and I can't help wondering
whether Debian should migrate to the pygame-ce fork as the upstream
for src:pygame-ce, but obviously that's out-of-scope for fixing a
FTBFS.
Do you think we should cherry-pick this patch or its equivalent into
pygame, then? I don't know this package especially well, but it looks
like a pretty simple patch.
Thanks,
--
Colin Watson (he/him) [[email protected]]
