There is no point uploading the requested version, 0.6.2, as Python3
support only arrived in 0.8.0 and Python2 packages are being removed
from the archive already.

I've had a look at packaging 0.8.0 and a few problems turn up.

0.8.0 is non-free, so a DFSG rebuild is needed to remove the RFCs and
fix up the doc generation support.

E: tftpy source: license-problem-non-free-RFC doc/rfc2347.txt
E: tftpy source: license-problem-non-free-RFC doc/rfc2348.txt
E: tftpy source: license-problem-non-free-RFC doc/rfc2349.txt
E: tftpy source: source-is-missing html/sphinx/_static/jquery.js line
length is 32714 characters (>512)
E: tftpy source: source-is-missing html/sphinx/_static/underscore.js
line length is 519 characters (>512)

A new docs package is probably required, along with an updated build
for the docs.

The distutils usage appears to have bitrotted and needs some attention.

The existing packaging is not ideal but moving to dh --with python3
also needs work to stop the package trying to run the tests as those
require network access (and seem to run forever in my builds).

The other packaging info needs updates as the upstream has moved from
SF to GitHub.

I have been able to test 0.8.0 using Python3 and it does work. However,
I only have a passing interest in tftpy and I may well be migrating to
alternative support for the one script which currently uses it. I'm not
willing to take on the package as maintainer and it's more work than
it's worth for a team upload.

If this update of the bug triggers anyone else to take it on, that
would be good but it is equally likely that the package will get
dropped as part of the python2 removal work.

-- 


Neil Williams
=============
http://www.linux.codehelp.co.uk/

Attachment: pgp6Z_fAhV_JD.pgp
Description: OpenPGP digital signature

Reply via email to