>   + I don't think I have been asked nor even contacted about the removal
>     despite being the maintainer.

i may have jumped the gun too quickly on this, probably by seeing PAPT
in the uploaders; apologies.

>  "dead  upstream" is  completely  wrong
>     considering that  the last  upstream release was  less than  a month
>     ago[0].
> [0] https://pypi.org/project/slapos.core/

interesting, as i've navigated thru their website to:

http://community.slapos.org/
->
http://community.slapos.org/source-control
->
http://git.erp5.org/gitweb

that shows no changes later than 3 years ago.

>   +  While I  agree that  the popcon  is very  low and  that I  have not
>     updated  it  for some  time,

As you know, any package in debian introduces an indirect "cost" to
the rest of the packages; in this case, we're trying to remove python2
from the distribution for bullseye release
(https://wiki.debian.org/Python/2Removal) and currently slapos.core
depends on ~20 packages (that means removing slapos.core will remove a
reverse depends on each one of the)

can we make slapos python3 compatible in Debian? in a timely manner?
If not, maybe RM it is the right approach?

-- 
Sandro "morph" Tosi
My website: http://sandrotosi.me/
Me at Debian: http://wiki.debian.org/SandroTosi
G+: https://plus.google.com/u/0/+SandroTosi

Reply via email to