Am Samstag, dem 18.12.2021 um 15:33 +0100 schrieb Sebastian Ramacher: > On 2021-12-18 15:05:18 +0100, Markus Koschany wrote: > > Am Samstag, dem 18.12.2021 um 12:49 +0100 schrieb Sebastian Ramacher: > > > Package: ftp.debian.org > > > Severity: normal > > > X-Debbugs-Cc: sramac...@debian.org, re...@packages.debian.org > > > > > > Please remove renpy from unstable. It was not included in bullseye since > > > it still depends on Python 2 (#938351). While there was some initial > > > progress to port it to Python 3, nothing seems to be happening since > > > over a year. See also https://github.com/renpy/renpy/issues/1098 which > > > seems to be stalled since 2019. renpy also needs to be updated from > > > libavresample to libswresample (#971325). So please remove it from > > > unstable. > > > > Please don't remove renpy from unstable yet. There is more than a year of > > time > > in the Bookworm release cycle. We are aware of the situation and I will > > request > > the removal next year if there is still no progress in regard to the port > > to > > Python 3. > > > > @Sebastian > > > > While I appreciate clean-ups, renpy is not an abandoned package. It would > > have > > been sensible to discuss the removal on the debian-devel-games list first. > > Pleast at least fix #971325. It's causing extra work (prop ups) during > bullseye stable releases for the FTP masters and the SRMs.
What kind of extra work is this causing in stable? We don't ship renpy in stable. I suggest to just ignore it. You also don't need to wait for any progress, you can just remove libavresample in unstable. It makes no difference if libavresample is removed from Build-Depends. The game still would be broken. Note that the reasoning for not removing renpy is to save all involved parties time by not having to go through NEW again if upstream finishes the port to Python 3 in the foreseeable future. Regards, Markus
signature.asc
Description: This is a digitally signed message part
