Re: python-opentracing

2019-10-25 Thread Fabrice BAUZAC-STEHLY
Dmitry Shachnev writes: > That happens because you are overriding dh_installdocs and running it only > for one package. > > Either remove the -ppython-opentracing-doc argument, or add another call > with --remaining-packages option. Thanks a lot, this has unblocked me. I'll continue working on

Bug#943496: RM: python-adns -- RoM; ancient; dead upstream; no Python 3 support and no reverse deps

2019-10-25 Thread Andrey Rahmatullin
Package: ftp.debian.org Severity: normal User: debian-python@lists.debian.org Usertags: py2removal https://pypi.org/project/adns-python/ no new releases since 2007. Popcon 544, because of transmission-remote-cli which was recently removed from the archive. Reverse deps checked with dak rm -Rnb

Re: Discussing next steps for the Python2 removal

2019-10-25 Thread Ondrej Novy
Hi, pá 25. 10. 2019 v 9:09 odesílatel Rebecca N. Palmer napsal: > Not the whole source package, but we do want to remove the py2 binary. > Maybe there should be two versions of the email, with the one for py2/3 > packages saying 'NMU' instead of 'removal'? > this is not how autorm works. You

Re: Discussing next steps for the Python2 removal

2019-10-25 Thread Ondrej Novy
Hi, pá 25. 10. 2019 v 3:30 odesílatel Sandro Tosi napsal: > do we really want to remove from testing (and subsequently from > debian, as mentioned below) if it both has a py2 and a py3k package? > should we limit this to py2-ONLY packages? > yes and no. If maintainer wants to keep package in

Re: Discussing next steps for the Python2 removal

2019-10-25 Thread Rebecca N. Palmer
Sandro Tosi wrote: do we really want to remove from testing (and subsequently from debian, as mentioned below) if it both has a py2 and a py3k package? should we limit this to py2-ONLY packages? Not the whole source package, but we do want to remove the py2 binary. Maybe there should be two