Re: Bug#943027: fretsonfire: Python2 removal in sid/bullseye
> > I agree. It's unreasonable to block this removal further. fretsonfire
> > is not a standalone package, but a part of a long chain of packages
> > affected by the Py2 removal and this can't wait longer.
> I completely disagree here. Fretsonfire is one package affected by the
> Py2 removal but certainly not the only one. If it was the only one, then
> there would be absolutely no question because the Py2 removal is more
> important than a single package. But it is not the only one. There is
> still a lot of time left, we are still in the middle of the release cycle.
if everybody would behave like that, we're end up with 3400 packages
still depending on python2.. there is time, yes, but it's less than
you may think. Do you realize Moritz replied to a message i sent on
Feb 1, which is 2 months ago: did something happened in between on the
side of porting fretsonfire to python3? did you do *anything* to port
it? how much more are we supposed to wait for that to magically
> What really saddens me is that people who either don't contribute or
> very little to Debian Games try to force their agenda one year before we
> freeze for Bullseye. I find that unacceptable to be honest. It's a slap
> in the face for contributors who have already ported several games to
> Python 3 and to be honest, it's a reason for me to quit this team
> altogether if you remove fretsonfire one year before the freeze.
if you want to quit, it's your choice obviously, but i'm not sure
rage-quitting ever worked. You're part of a distribution, and weather
you like it or not, every package as a "weight" in it, currently
fretsonfire is preventing progress in the direction the distribution
has decided to go, which is to remove python2.
i wasnt aware that being part of the games team was a requirement to
tell you that fretsonfire is not good enough to be kept in Debian in
its current form, i thought being a DD was a good enough quality
already, and you already had 2 DDs telling you that. more on a
personal note, this package forces me to keep 2 packages i maintain in
debian, which i would be happily get RM'ed - how long should i wait
for you to start porting fretonfire?
> > If anyone ports it to Py3 until Bullseye freeze, even better. Failing
> > that, it's still available on Flathub for every future Debian user:
> > https://www.flathub.org/apps/details/net.sourceforge.fretsonfire
> Sure, maybe we should just direct all of our users to flathub for all
> our non-essential and non-important packages. Let's focus on the Linux
> kernel, systemd, and some GNU tools only, that's the universal operating
> system for you kids.
you may want to watch your tone, it's becoming inappropriate and
Sandro "morph" Tosi
My website: http://sandrotosi.me/
Me at Debian: http://wiki.debian.org/SandroTosi