Bug#850664: RFS: python-pynzb/0.1.0-3

2017-01-11 Thread Carl Suster
Control: tag -1 -moreinfo Hi Sean, I think you forgot to `git push` :) Oops! Done. Also, it would be good if you could use the Forwarded: header to indicate whether your patches have been sent upstream or not. This is especially useful in team-maintained packages. If you add this now,

Bug#850664: RFS: python-pynzb/0.1.0-3

2017-01-11 Thread Sean Whitton
control: tag -1 +moreinfo Hello Carl, I think you forgot to `git push` :) Also, it would be good if you could use the Forwarded: header to indicate whether your patches have been sent upstream or not. This is especially useful in team-maintained packages. If you add this now, don't forget

Bug#850664: RFS: python-pynzb/0.1.0-3

2017-01-11 Thread Carl Suster
Hi Gianfranco, Thanks for your comments! what about calling 2to3 in setup.py? I somehow overlooked that this was possible. That's much more sensible than what I was doing. and you can patch the code with a retro-compatible code if you can't find a way that works with both python2 and

Bug#850664: RFS: python-pynzb/0.1.0-3

2017-01-10 Thread Gianfranco Costamagna
Hello, >-export PYBUILD_AFTER_BUILD_python3=2to3 -n -w {build_dir}/pynzb/; sed -i -e >'s/StringIO/BytesIO/g' -e 's/BytesIO(xml)/BytesIO(bytes(xml,"utf-8"))/' >{build_dir}/pynzb/lxml_nzb.py >+export PYBUILD_AFTER_BUILD_python3=2to3-{version} -n -w {build_dir}/pynzb/; >sed >-i -e

Bug#850664: RFS: python-pynzb/0.1.0-3

2017-01-10 Thread Carl Suster
Control: tag -1 -moreinfo Hi Sean, Sorry about that. At your prompting I've installed sbuild and now the package builds successfully in a chroot for unstable using sbuild -A. I've uploaded a new version to git and mentors, with the diff below since the version you last saw. As you can see I

Bug#850664: RFS: python-pynzb/0.1.0-3

2017-01-10 Thread Sean Whitton
control: tag -1 +moreinfo control: owner -1 ! Dear Carl, Before we go any further with this one, I regret to inform you that it fails to build. See the attached log. -- Sean Whitton sbuild (Debian sbuild) 0.72.0 (25 Oct 2016) on iris.silentflame.com

Bug#850664: RFS: python-pynzb/0.1.0-3

2017-01-09 Thread Carl Suster
Control: tag -1 -moreinfo Hi Sean, Thanks for your review! The Python 2 module can still be built fine, but I removed it since there were no rdeps. As in my reponse to your other RFS, I'd like to confirm that this is DPMT policy. I don't think that it's a team policy specifically, I was

Bug#850664: RFS: python-pynzb/0.1.0-3

2017-01-09 Thread Sean Whitton
control: tag -1 +moreinfo Dear Carl, On Mon, Jan 09, 2017 at 12:56:51PM +1100, Carl Suster wrote: > I am looking for a sponsor for my package "python-pynzb" Thank you for your interest! > The Python 2 module can still be built fine, but I removed it since > there were no rdeps. As in my

Bug#850664: RFS: python-pynzb/0.1.0-3

2017-01-08 Thread Carl Suster
Package: sponsorship-requests Severity: normal Dear mentors, I am looking for a sponsor for my package "python-pynzb" * Package name: python-pynzb Version : 0.1.0-3 * URL : https://github.com/ericflo/pynzb * License : BSD-3-clause Section : python I