Your message dated Wed, 30 Nov 2022 18:22:10 +0100
with message-id <[email protected]>
and subject line zorp: Python2 removal in Debian sid/bookworm
has caused the Debian Bug report #1008285,
regarding Should zorp be removed?
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact [email protected]
immediately.)
--
1008285: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1008285
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Source: zorp
Version: 7.0.1~alpha2-3
Severity: serious
Your package came up as a candidate for removal from Debian:
- Last upload in 2019, removed from testing since 2017
- Still depends on Python 2.7 and thus RC-buggy
If you disagree and want to continue to maintain this package,
please just close this bug (and fix the open issues).
If you agree with the removal, please reassign to ftp.debian.org
by sending the following commands to [email protected]:
--------------------------------------
severity $BUGNUM normal
reassign $BUGNUM ftp.debian.org
retitle $BUGNUM RM: <package> -- RoM; <reasons>
thx
--------------------------------------
Otherwise I'll move forward and request it's removal in a month.
Cheers,
Moritz
--- End Message ---
--- Begin Message ---
Control: retitle 938921 RM: zorp -- RoQA; py2 leftover
On Thu, 5 May 2022 10:20:23 +0200 [email protected] wrote:
We are in a process of re-writing our code, which will address (among
others) the problems listed in the issue. However it will take quite
some time so our estimation is about Autumn 2022 (Oct) when we will get
there.
Is the possible not to remove our package from Debian repository and
close this case so that we do not need to go through the process again
to get it back there later on?
It does not seem like there has been any work put in to port zorp to Python 3.
October has passed...
--- End Message ---
