On Sun, 28 Jan 2024 at 22:49:37 +0100, Alexandre Detiste wrote: > Le jeu. 25 janv. 2024 à 11:15, Simon McVittie <s...@debian.org> a écrit : > > I also don't understand where these new upstream releases are coming from, > > because https://github.com/renpy/pygame_sdl2 only has tags for 8.1.0, > > and there don't seem to be any recent commits that are relevant to > > cython3 compatibility. > > The release are coming from here. > https://www.renpy.org/latest.html
Oh, do those tarball code-drops have changes that are newer than what's in https://github.com/renpy/pygame_sdl2 git? > pygame-sdl2 state (which is a very old fork of pygame) is in limbo, > upstream is considering vendoring it inside the main tarball > it is maybe already maintained in the main git three. I see. Do I understand correctly that we would consider it to be a bug for anything other than renpy to use pygame-sdl2? If so, I think if I was the Debian maintainer of these packages, I'd be very tempted to vendor pygame-sdl2 into renpy (using dpkg's multiple-.orig-tarballs feature if upstream have not done similar vendoring) so that there's only one Debian source package to keep track of, and no possibility of version skew between renpy and its pygame fork. smcv
