On 2/2/20 8:39 PM, Sandro Tosi wrote:
$ apt-cache rdepends python-gmpy
python-gmpy
Reverse Depends:
obfsproxy
python-tlslite-ng
python-sympy
python-gmpy-doc
Dependencies on obfsproxy and python-sympy documented with affects and
blocks. python-tlslite-ng has been removed already,
there are no more reverse dependencies on python-gmpy, what should we
do next? i see the source package doesnt produce any python3 package,
and the last changelog entry contains:
* Override python-foo-but-no-python3-foo Lintian warning, since this package
is end-of-life after Python 2 support ends.
should we remove this package then? or do you want to generate a python3-gmpy?
I didn't realize, but it looks like this package actually does support
Python 3. I had assumed we would let this package die when Python 2
dies, since the package is dead upstream since 2013. However, looking at
the popcon stats, the original python GMPY is still much more popular
than than python GMPY2 (3543 vs 443). So I think it's worth keeping this
package.
I'm working on converting it over now and should be able to get it done
in the next few weeks.
Is it possible to remove the AUTORM tag until this is done, or should we
let it get deleted and upload a new python3-gmpy package after that?
and we can rename
python-gmpy-doc to python3-gmpy-doc once the blocking bugs are resolved.
please dont, -doc package must preserve the python- prefix.
Cheers,
Sandro
