Your message dated Thu, 09 Jan 2020 06:17:35 +0000
with message-id <[email protected]>
and subject line Bug#948162: Removed package(s) from unstable
has caused the Debian Bug report #948162,
regarding RM: python-peak.util -- RoQA; python2-only; combination of modules 
most of which deprecated, no py3k available
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.)


-- 
948162: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=948162
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Source: python-peak.util
Severity: serious

Hello,
this package recently became a leaf pkg and it's currently python2-only; looking
at how it's made of, it appears it's a combination of modules:


Module             Current  Latest     py3k
                   Version  Available  available?
--------------------------------------------------------
addons             0.7      0.7        some py3k support
bytecodeassembler  0.6      0.6.1      no
extremes           1.1.1    1.1.1      yes
proxies            0.9      0.10.0     yes
symboltype         1.0      1.0        yes

What are the plans for this package? they mostly leave at the new upstream
location on github https://github.com/PEAK-Legacy which says "Projects from the
Python Enterprise Application Kit that are not actively in development, or have
been discontinued. Most are Python 2-only."

Should we just go ahead and remove this package, since there are no more Debian
packages depending on it?

If i dont hear back within a week with a good reason to keep this package
around, i'll file for its removal.

Regards,
Sandro


-- System Information:
Debian Release: 10.0
  APT prefers unstable-debug
  APT policy: (500, 'unstable-debug'), (500, 'unstable'), (1, 
'experimental-debug'), (1, 'experimental')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 4.19.0-5-amd64 (SMP w/8 CPU cores)
Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_OOT_MODULE, 
TAINT_UNSIGNED_MODULE
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE= 
(charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Versions of packages python-peak.util depends on:
ii  python                       2.7.16-1
pn  python-peak.util.decorators  <none>

python-peak.util recommends no packages.

python-peak.util suggests no packages.

--- End Message ---
--- Begin Message ---
We believe that the bug you reported is now fixed; the following
package(s) have been removed from unstable:

python-turbojson |  1.3.2-2.1 | all
 turbojson |  1.3.2-2.1 | source

------------------- Reason -------------------
RoQA; python2-only; needs python-peak.rules, which is being removed, no py3k 
available
----------------------------------------------

Note that the package(s) have simply been removed from the tag
database and may (or may not) still be in the pool; this is not a bug.
The package(s) will be physically removed automatically when no suite
references them (and in the case of source, when no binary references
it).  Please also remember 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.

Packages are usually not removed from testing by hand. Testing tracks
unstable and will automatically remove packages which were removed
from unstable when removing them from testing causes no dependency
problems. The release team can force a removal from testing if it is
really needed, please contact them if this should be the case.

We try to close bugs which have been reported against this package
automatically. But please check all old bugs, if they were closed
correctly or should have been re-assigned to another package.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to [email protected].

The full log for this bug can be viewed at https://bugs.debian.org/948162

This message was generated automatically; if you believe that there is
a problem with it please contact the archive administrators by mailing
[email protected].

Debian distribution maintenance software
pp.
Scott Kitterman (the ftpmaster behind the curtain)

--- End Message ---

Reply via email to