Debian Bug report logs - #943027
fretsonfire: Python2 removal in sid/bullseye

Toggle useless messages

Message #5 received at maintonly@bugs.debian.org (full text, mbox, reply):

From: morph@debian.org

To: maintonly@bugs.debian.org

Subject: fretsonfire: Python2 removal in sid/bullseye

Date: Wed, 23 Oct 2019 02:33:25 +0000

Source: fretsonfire
Version: 1.3.110.dfsg2-5
Severity: normal
Tags: sid bullseye
User: debian-python@lists.debian.org
Usertags: py2removal

Python2 becomes end-of-live upstream, and Debian aims to remove
Python2 from the distribution, as discussed in
https://lists.debian.org/debian-python/2019/07/msg00080.html

Your package either build-depends, depends on Python2, or uses Python2
in the autopkg tests (the specific reason can be found searching this
source package in
https://people.debian.org/~morph/mass-bug-py2removal_take2.txt ).
Please stop using Python2, and fix this issue by one of the following
actions.

- Convert your Package to Python3. This is the preferred option.  In
  case you are providing a Python module foo, please consider dropping
  the python-foo package, and only build a python3-foo package.  Please
  don't drop Python2 modules, which still have reverse dependencies,
  just document them.
  
  This is the preferred option.

- If the package is dead upstream, cannot be converted or maintained
  in Debian, it should be removed from the distribution.  If the
  package still has reverse dependencies, raise the severity to
  "serious" and document the reverse dependencies with the BTS affects
  command.  If the package has no reverse dependencies, confirm that
  the package can be removed, reassign this issue to ftp.debian.org,
  make sure that the bug priority is set to normal and retitle the
  issue to "RM: PKG -- removal triggered by the Python2 removal".

- If the package has still many users (popcon >= 300), or is needed to
  build another package which cannot be removed, document that by
  adding the "py2keep" user tag (not replacing the py2remove tag),
  using the debian-python@lists.debian.org user.  Also any
  dependencies on an unversioned python package (python, python-dev)
  must not be used, same with the python shebang.  These have to be
  replaced by python2/python2.7 dependencies and shebang.

  This is the least preferred option.

If there are questions, please refer to the wiki page for the removal:
https://wiki.debian.org/Python/2Removal, or ask for help on IRC
#debian-python, or the debian-python@lists.debian.org mailing list.

Message #22 received at 943027@bugs.debian.org (full text, mbox, reply):

From: Sandro Tosi <sandro.tosi@gmail.com>

To: 943027@bugs.debian.org, Debian Games Team <pkg-games-devel@lists.debian.org>, Debian Games Team <pkg-games-devel@alioth-lists.debian.net>, Miriam Ruiz <miriam@debian.org>, Barry deFreese <bdefreese@debian.org>

Subject: Re: fretsonfire: Python2 removal in sid/bullseye

Date: Fri, 31 Jan 2020 23:09:06 -0500

Hello everyone,

On Wed, 23 Oct 2019 02:33:25 +0000 morph@debian.org wrote:
> Source: fretsonfire
> Version: 1.3.110.dfsg2-5
> Severity: normal
> Tags: sid bullseye
> User: debian-python@lists.debian.org
> Usertags: py2removal

what is the future of fretsonfire in Debian? the version we have in
the archive is from 2009 (!), and i could not find any signal of
recent development from upstream. Nor i could find a proper port to
python3 (the one that gets closer is fofix, but there's still quite a
lot of work to do:
https://fofix.github.io/blog/moving-to-python3.html).

Should we just remove the package from Debian, and wait for a better
port to be published?

I'd like to not wait a long time, so if i dont hear back within a week
with a good reason to keep the package in Debian, i'll file for its
removal.

Regards,
Sandro

Message #27 received at 943027@bugs.debian.org (full text, mbox, reply):

From: Markus Koschany <apo@debian.org>

To: Sandro Tosi <sandro.tosi@gmail.com>

Cc: 943027@bugs.debian.org, "debian-devel-games@lists.debian.org" <debian-devel-games@lists.debian.org>

Subject: Re: Bug#943027: fretsonfire: Python2 removal in sid/bullseye

Date: Sat, 1 Feb 2020 16:06:56 +0100

[Message part 1 (text/plain, inline)]

Hello,

Am 01.02.20 um 05:09 schrieb Sandro Tosi:
> Hello everyone,
> 
> On Wed, 23 Oct 2019 02:33:25 +0000 morph@debian.org wrote:
>> Source: fretsonfire
>> Version: 1.3.110.dfsg2-5
>> Severity: normal
>> Tags: sid bullseye
>> User: debian-python@lists.debian.org
>> Usertags: py2removal
> 
> what is the future of fretsonfire in Debian? the version we have in
> the archive is from 2009 (!), and i could not find any signal of
> recent development from upstream. Nor i could find a proper port to
> python3 (the one that gets closer is fofix, but there's still quite a
> lot of work to do:
> https://fofix.github.io/blog/moving-to-python3.html).
> 
> Should we just remove the package from Debian, and wait for a better
> port to be published?
> 
> I'd like to not wait a long time, so if i dont hear back within a week
> with a good reason to keep the package in Debian, i'll file for its
> removal.

Please don't remove any games from Debian because of the Python 2
removal and try to port the games to Python 3 instead. For instance
Bernhard has done a lot of good porting work and ported several games to
Python 3 already. Even if we don't succeed in porting all games to
Python 3 in time for Debian 11, then we should just give people more
time to realize the impact of the py2removal goal.

Regards,

Markus

[signature.asc (application/pgp-signature, attachment)]

Message #32 received at 943027@bugs.debian.org (full text, mbox, reply):

From: Steve Cotton <steve@octalot.at>

To: Markus Koschany <apo@debian.org>

Cc: Sandro Tosi <sandro.tosi@gmail.com>, 943027@bugs.debian.org, "debian-devel-games@lists.debian.org" <debian-devel-games@lists.debian.org>

Subject: Re: Bug#943027: fretsonfire: Python2 removal in sid/bullseye

Date: Sat, 1 Feb 2020 17:06:49 +0100

On Sat, Feb 01, 2020 at 04:06:56PM +0100, Markus Koschany wrote:
> Please don't remove any games from Debian because of the Python 2
> removal and try to port the games to Python 3 instead. For instance
> Bernhard has done a lot of good porting work and ported several games to
> Python 3 already. Even if we don't succeed in porting all games to
> Python 3 in time for Debian 11, then we should just give people more
> time to realize the impact of the py2removal goal.

Markus, the trouble with saying "give people more time" is that there's been
a py2removal bug open on Frets On Fire since October 2018. That's #912511,
from the python-pygame mass bug filing.

BR,
Steve

Message #37 received at 943027@bugs.debian.org (full text, mbox, reply):

From: Markus Koschany <apo@debian.org>

To: Steve Cotton <steve@octalot.at>

Cc: Sandro Tosi <sandro.tosi@gmail.com>, 943027@bugs.debian.org, "debian-devel-games@lists.debian.org" <debian-devel-games@lists.debian.org>

Subject: Re: Bug#943027: fretsonfire: Python2 removal in sid/bullseye

Date: Sat, 1 Feb 2020 17:23:48 +0100

[Message part 1 (text/plain, inline)]

Am 01.02.20 um 17:06 schrieb Steve Cotton:
> On Sat, Feb 01, 2020 at 04:06:56PM +0100, Markus Koschany wrote:
>> Please don't remove any games from Debian because of the Python 2
>> removal and try to port the games to Python 3 instead. For instance
>> Bernhard has done a lot of good porting work and ported several games to
>> Python 3 already. Even if we don't succeed in porting all games to
>> Python 3 in time for Debian 11, then we should just give people more
>> time to realize the impact of the py2removal goal.
> 
> Markus, the trouble with saying "give people more time" is that there's been
> a py2removal bug open on Frets On Fire since October 2018. That's #912511,
> from the python-pygame mass bug filing.

We have one year left in this release cycle and you cannot expect that
all Python 2 games will be ported to Python 3 at the same time or in a
few months. There is no urgency at all to remove those games from
Debian. It also does not matter how old a game is because games like
fretsonfire are feature complete. Please contribute by fixing those bugs
for a change.

[signature.asc (application/pgp-signature, attachment)]

Message #42 received at 943027@bugs.debian.org (full text, mbox, reply):

From: Sandro Tosi <morph@debian.org>

To: Markus Koschany <apo@debian.org>

Cc: Steve Cotton <steve@octalot.at>, 943027@bugs.debian.org, "debian-devel-games@lists.debian.org" <debian-devel-games@lists.debian.org>

Subject: Re: Bug#943027: fretsonfire: Python2 removal in sid/bullseye

Date: Sat, 1 Feb 2020 11:59:33 -0500

> Am 01.02.20 um 17:06 schrieb Steve Cotton:
> > On Sat, Feb 01, 2020 at 04:06:56PM +0100, Markus Koschany wrote:
> >> Please don't remove any games from Debian because of the Python 2
> >> removal and try to port the games to Python 3 instead. For instance

who should port these games? the upstream maintaintainers? maybe but
what if they are not developing the game anymore? the debian
maintainers? i dont think that's appropriate to ask that, as then even
more burden will fall on them (both keeping the package up to
standards *and* maintain the py3k port). so whos left? it appears
nobody.

> >> Bernhard has done a lot of good porting work and ported several games to
> >> Python 3 already. Even if we don't succeed in porting all games to
> >> Python 3 in time for Debian 11, then we should just give people more
> >> time to realize the impact of the py2removal goal.

No. with this approach, nobody will do anything about py2removal and
we're gonna keep python2 around forever. you had more than a year,
nothing happen, it's time to be objective and realize there wont be a
savior for fretsonfire and it's time for Debian to drop it.

> >
> > Markus, the trouble with saying "give people more time" is that there's been
> > a py2removal bug open on Frets On Fire since October 2018. That's #912511,
> > from the python-pygame mass bug filing.
>
> We have one year left in this release cycle and you cannot expect that

no we dont. at some point in the next months the distribution will
freeze and we wont be able to make substantial progress.

> all Python 2 games will be ported to Python 3 at the same time or in a
> few months. There is no urgency at all to remove those games from
> Debian.

really? what about all the reverse dependencies that need to be kept
in the archive *just* for this antique softwares to remain usable? I,
for example, have 2 packages i cant remove because of fretsonfire; at
some point i'll have to make a decision, and most likely i'll favor my
own packages over a relic from 10+ years ago.

> It also does not matter how old a game is because games like
> fretsonfire are feature complete.

OMG LOL! did you look at the sourceforge page? there are literally
hundreds of bug reports and feature requests. year "feature complete".

> Please contribute by fixing those bugs
> for a change.

i sincerely hope this is not meant for me.

Please revisit your position to make the Debian distribution progress
towards the py2removal goal: dont be an obstacle, help instead.

Regard,s
-- 
Sandro "morph" Tosi
My website: http://sandrotosi.me/
Me at Debian: http://wiki.debian.org/SandroTosi
Twitter: https://twitter.com/sandrotosi

Message #49 received at 943027@bugs.debian.org (full text, mbox, reply):

From: Moritz Mühlenhoff <jmm@inutil.org>

To: Sandro Tosi <morph@debian.org>

Cc: Markus Koschany <apo@debian.org>, Steve Cotton <steve@octalot.at>, 943027@bugs.debian.org, "debian-devel-games@lists.debian.org" <debian-devel-games@lists.debian.org>

Subject: Re: Bug#943027: fretsonfire: Python2 removal in sid/bullseye

Date: Fri, 27 Mar 2020 22:41:16 +0100

On Sat, Feb 01, 2020 at 11:59:33AM -0500, Sandro Tosi wrote:
> > Am 01.02.20 um 17:06 schrieb Steve Cotton:
> > > On Sat, Feb 01, 2020 at 04:06:56PM +0100, Markus Koschany wrote:
> > >> Please don't remove any games from Debian because of the Python 2
> > >> removal and try to port the games to Python 3 instead. For instance
> 
> who should port these games? the upstream maintaintainers? maybe but
> what if they are not developing the game anymore? the debian
> maintainers? i dont think that's appropriate to ask that, as then even
> more burden will fall on them (both keeping the package up to
> standards *and* maintain the py3k port). so whos left? it appears
> nobody.

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.

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

Cheers,
        Moritz

Message #54 received at 943027@bugs.debian.org (full text, mbox, reply):

From: Markus Koschany <apo@debian.org>

To: Moritz Mühlenhoff <jmm@inutil.org>

Cc: Sandro Tosi <morph@debian.org>, Steve Cotton <steve@octalot.at>, 943027@bugs.debian.org, "debian-devel-games@lists.debian.org" <debian-devel-games@lists.debian.org>

Subject: Re: Bug#943027: fretsonfire: Python2 removal in sid/bullseye

Date: Fri, 27 Mar 2020 23:08:22 +0100

[Message part 1 (text/plain, inline)]

Am 27.03.20 um 22:41 schrieb Moritz Mühlenhoff:
[...]
> 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.

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 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.

[signature.asc (application/pgp-signature, attachment)]

Message #59 received at 943027@bugs.debian.org (full text, mbox, reply):

From: Sandro Tosi <morph@debian.org>

To: Markus Koschany <apo@debian.org>

Cc: Moritz Mühlenhoff <jmm@inutil.org>, Steve Cotton <steve@octalot.at>, 943027@bugs.debian.org, "debian-devel-games@lists.debian.org" <debian-devel-games@lists.debian.org>

Subject: Re: Bug#943027: fretsonfire: Python2 removal in sid/bullseye

Date: Fri, 27 Mar 2020 23:40:04 -0400

> > 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
happen?

> 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
definitely unhelpful.

Regards.
-- 
Sandro "morph" Tosi
My website: http://sandrotosi.me/
Me at Debian: http://wiki.debian.org/SandroTosi
Twitter: https://twitter.com/sandrotosi

Message #64 received at 943027@bugs.debian.org (full text, mbox, reply):

From: Sylvain Beucler <beuc@beuc.net>

To: Sandro Tosi <morph@debian.org>, Markus Koschany <apo@debian.org>

Cc: Moritz Mühlenhoff <jmm@inutil.org>, Steve Cotton <steve@octalot.at>, 943027@bugs.debian.org, "debian-devel-games@lists.debian.org" <debian-devel-games@lists.debian.org>

Subject: Re: Bug#943027: fretsonfire: Python2 removal in sid/bullseye

Date: Sat, 28 Mar 2020 10:06:58 +0100

Hi,

On 28/03/2020 04:40, Sandro Tosi wrote:
> you may want to watch your tone, it's becoming inappropriate and
> definitely unhelpful.

Everybody, please use a more measured tone.
(Sandro, I feel your tone was on par with those you criticize!)


From what I understand it would be good to set a deadline in advance for
this issue to be resolved.
What are your suggestions?

Cheers!
Sylvain

Message #69 received at 943027@bugs.debian.org (full text, mbox, reply):

From: Markus Koschany <apo@debian.org>

To: Sandro Tosi <morph@debian.org>

Cc: Moritz Mühlenhoff <jmm@inutil.org>, Steve Cotton <steve@octalot.at>, 943027@bugs.debian.org, "debian-devel-games@lists.debian.org" <debian-devel-games@lists.debian.org>

Subject: Re: Bug#943027: fretsonfire: Python2 removal in sid/bullseye

Date: Sat, 28 Mar 2020 14:54:42 +0100

[Message part 1 (text/plain, inline)]

Am 28.03.20 um 04:40 schrieb Sandro Tosi:
>>> 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
> happen?

I suggest that you either read my blog [1] or subscribe to
pkg-games-devel to understand what we as a team and I have been doing.
As a matter of fact we have fixed several Py2 removal bugs by porting
games to Python 3 already. Naturally there are only so many contributors
who can work on so many packages in their free time and there is no
guarantee in which order certain bugs are fixed. That means if you don't
contribute to the solution of the problem in other ways than simply
demanding the removal of a package, then it will take as long as it takes.

>> 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.

Debian is a collaborative effort to create a free operating system.
There are always technical and social implications. On the technical
side we have a release goal to remove Python 2 which is a huge
undertaking because thousands of packages depend on Python 2. There are
several possible solutions to achieve that goal including porting to
Python 3 or patching packages. Removing packages without the consent of
the maintainer in the middle of a release cycle is considered to be
antisocial. Python 2 is not the only problem, we also receive reports
about failing packages because of changes to SDL2 or the C/C++ compiler.
All these issues have to be addressed in time and your bug report is not
anything special.

> 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?

Being part of the games team is a requirement to file removal bug
reports as the maintainer. Again requesting the removal of a package in
the middle of the release cycle without the consent of the maintainer is
rude and antisocial. If you don't want to maintain your packages any
longer than I suggest you orphan them, so that I can take care of them
until we freeze for Bullseye. If fretsonfire bug 943027 has not been
fixed by then and the release team decides that we go ahead with the Py2
removal, then fretsonfire and its dependencies will be removed and I
will request the removal myself.


>>> 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
> definitely unhelpful.

I find that funny when I have told you in a private email before to
reflect on your own behavior once in a while. If you send disrespectful
messages like that [2] then you have missed the point entirely.

Markus Koschany


P.S.: It's called sarcasm.

[1] https://gambaru.de/blog/tag/planetdebian/
[2] https://lists.debian.org/debian-devel-games/2020/02/msg00003.html

[signature.asc (application/pgp-signature, attachment)]

Message #74 received at 943027@bugs.debian.org (full text, mbox, reply):

From: Moritz Mühlenhoff <jmm@inutil.org>

To: Markus Koschany <apo@debian.org>

Cc: Sandro Tosi <morph@debian.org>, Moritz Mühlenhoff <jmm@inutil.org>, Steve Cotton <steve@octalot.at>, 943027@bugs.debian.org, "debian-devel-games@lists.debian.org" <debian-devel-games@lists.debian.org>

Subject: Re: Bug#943027: fretsonfire: Python2 removal in sid/bullseye

Date: Sat, 28 Mar 2020 15:40:58 +0100

On Sat, Mar 28, 2020 at 02:54:42PM +0100, Markus Koschany wrote:
> If fretsonfire bug 943027 has not been
> fixed by then and the release team decides that we go ahead with the Py2
> removal, then fretsonfire and its dependencies will be removed and I
> will request the removal myself.

If you want to keep it in the archive until the freeze, so be it.
It will however soon become uninstallable as reverse dependencies
drop their Python 2 packages.

Cheers,
        Moritz

Message #87 received at 943027@bugs.debian.org (full text, mbox, reply):

From: Markus Koschany <apo@debian.org>

To: 697615@bugs.debian.org, 900890@bugs.debian.org, 936796@bugs.debian.org, 938509@bugs.debian.org, 943027@bugs.debian.org, 956335@bugs.debian.org, 961932@bugs.debian.org

Subject: Intent to request the removal from Debian

Date: Mon, 21 Dec 2020 14:03:10 +0100

[Message part 1 (text/plain, inline)]

Hi,

as previously announced on debian-devel-games [1] I intend to request the
removal of this source or binary package from Debian at the end of January
2021. If you are interested in fixing this bug, please let me know in time to
avoid the removal from Debian.

Markus


[1] https://lists.debian.org/debian-devel-games/2020/12/msg00013.html

[signature.asc (application/pgp-signature, inline)]

Message #92 received at 943027-done@bugs.debian.org (full text, mbox, reply):

From: Debian FTP Masters <ftpmaster@ftp-master.debian.org>

To: 427164-done@bugs.debian.org,428346-done@bugs.debian.org,428351-done@bugs.debian.org,428352-done@bugs.debian.org,483445-done@bugs.debian.org,483451-done@bugs.debian.org,608245-done@bugs.debian.org,912511-done@bugs.debian.org,943027-done@bugs.debian.org,956335-done@bugs.debian.org,

Cc: fretsonfire@packages.debian.org

Subject: Bug#983124: Removed package(s) from unstable

Date: Sun, 28 Feb 2021 12:27:51 +0000

Version: 1.3.110.dfsg2-5+rm

Dear submitter,

as the package fretsonfire has just been removed from the Debian archive
unstable we hereby close the associated bug reports.  We are sorry
that we couldn't deal with your issue properly.

For details on the removal, please see https://bugs.debian.org/983124

The version of this package that was in Debian prior to this removal
can still be found using http://snapshot.debian.org/.

Please note that the changes have been done on the master archive and
will not propagate to any mirrors until the next dinstall run at the
earliest.

This message was generated automatically; if you believe that there is
a problem with it please contact the archive administrators by mailing
ftpmaster@ftp-master.debian.org.

Debian distribution maintenance software
pp.
Joerg Jaspert (the ftpmaster behind the curtain)

Send a report that this bug log contains spam.