Bug#1038073: magicmaze: Indirectly depends on SDL 1.2

[Petter Reinholdtsen <pere@hungry.com>]

Control: reopen -1
Control: found -1 1.5.1+dfsg-1

I no longer believe this is solved.  I probably messed up the packaging.
In any case, from #debian-games today:


<smcv> pere: magicmaze Depends on ruby-sdl which Depends on
       libsdl1.2debian, so no it is not solved

<smcv> pere: (I can tell that from packages.debian.org, no need to
       actually install it or know anything about Ruby)

<smcv> pere: please reopen the bug, and if the way to make it use SDL2
       is via ruby-sdl2, block it by a RFP (or ITP) for ruby-sdl2

<smcv> pere: fyi the most-correct way to tell "does it use SDL 1?" would
       be to read /proc/$pid/maps and if you see libSDL-1.2.so.* then
       yes it does

<smcv> pere: since bookworm, our libSDL-1.2.so.0 is actually a wrapper
       around SDL2, but the SDL 1.2 API has plenty of known problems, so
       I still consider it to be a (non-RC!) bug if games need to use
       that wrapper

<pere> smcv: aha. I guess upstream need some feedback, then. :)

<smcv> pere: sorry, *since trixie

<vv221> smcv, can we plan on the SDL 1 → 2 wrapper to stay around
        ~indefinitely? For some non-free games that are never going to
        be updated again, it is really useful.

<vv221> (side note, it’s really nice that we can chain the SDL 1 → 2 → 3
        wrappers)

<smcv> pere: if upstream has implemented runtime switching between
       ruby-sdl for SDL 1.2 and ruby-sdl2 for SDL 2, then it's a
       downstream bug: someone needs to package ruby-sdl2, and then make
       magicmaze use that instead of ruby-sdl

<smcv> pere: or if upstream unconditionally uses ruby-sdl and therefore
       SDL 1.2, it's an upstream bug

<smcv> pere: I don't know which

<pere> it seemed to implement an alternative drawing mechanism, but I do
       not know any details.  check the code. :) My project for the
       package was to migrate its packagint to git, which is complete.

<smcv> vv221: I don't intend to remove sdl12-compat any time soon, but I
       *do* want to start removing the SDL 1.2
       mixer/image/net/... libraries, which are totally unmaintained and
       sometimes security-sensitive

<vv221> OK, this might cause problems for said games. Could wrappers for
        some of these be done, or is it a lost cause?

<smcv> pere: oh if you're just doing QA work on it, then you can leave
       that analysis to whoever eventually adopts it (if they exist),
       but please do reopen the bug

<vv221> I don’t have the skills to write such wrappers myself yet, but
        since they would be required for my favourite non-free game I
        would be willing to learn and give it a try.

<pere> I'll cut-n-paste this dialog into the bts. :)

-- 
Happy hacking
Petter Reinholdtsen