Bug#948162: python-peak.util: should this package be removed?

2020-01-07 Thread Sandro Tosi
> I'm in a hurry right now, I will try to file it tomorrow, but please go ahead
> if you have time, no need to wait and thanks for pushing this!

I've reassigned this bug to ftp.d.o -- thanks!

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



Bug#948162: python-peak.util: should this package be removed?

2020-01-07 Thread Daniele Tricoli
Hello Sandro,

On Sat, Jan 04, 2020 at 03:03:59PM -0500, Sandro Tosi wrote:
> 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.7some py3k support
> bytecodeassembler  0.6  0.6.1  no
> extremes   1.1.11.1.1  yes
> proxies0.9  0.10.0 yes
> symboltype 1.0  1.0yes
> 
> 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?

I agree with you (I made tha same search in the past about upstream status and
I reached your same conclusion): I was waiting for the package to became a leaf
package before filing for its removal.

I'm in a hurry right now, I will try to file it tomorrow, but please go ahead
if you have time, no need to wait and thanks for pushing this!

Regards,

-- 
  Daniele Tricoli 'eriol'
  https://mornie.org


signature.asc
Description: PGP signature


Bug#948162: python-peak.util: should this package be removed?

2020-01-04 Thread Sandro Tosi
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.7some py3k support
bytecodeassembler  0.6  0.6.1  no
extremes   1.1.11.1.1  yes
proxies0.9  0.10.0 yes
symboltype 1.0  1.0yes

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  

python-peak.util recommends no packages.

python-peak.util suggests no packages.