Bug#1084800: RFS: nxt-python/3.3.0-1 [ITP] -- Python driver/interface/wrapper for the LEGO Mindstorms NXT robot
Package: sponsorship-requests
Severity: important
Dear mentors,
I am looking for a sponsor for my package "nxt-python":
* Package name : nxt-python
Version : 3.3.0-1
Upstream contact : NXT-Python mailing list <~ni/nxt-python@lists.sr.ht>
* URL : https://sr.ht/~ni/nxt-python/
* License : MIT, GPL-3+
* Vcs : https://salsa.debian.org/debian-lego-team/nxt-python
Section : python
The source builds the following binary packages:
python3-nxt - Python driver/interface/wrapper for the LEGO Mindstorms NXT robot
To access further information about this package, please visit the following URL:
https://mentors.debian.net/package/nxt-python/
Alternatively, you can download the package with 'dget' using this command:
dget -x https://mentors.debian.net/debian/pool/main/n/nxt-python/nxt-python_3.3.0-1.dsc
Changes since the last upload:
nxt-python (3.3.0-1) unstable; urgency=medium
.
* Update watch file and git buildpackage configuration.
* New upstream version 3.3.0:
- Use GObject Introspection bindings and gtk3. (Closes: #885467)
- Use Python 3. (Closes: #937175)
- Use pyusb>1.0. (Closes: #773201)
* Upgrade packaging for nxt-python reintroduction: (Closes: #1083009)
- Bump standards version to 4.7.0.
- Build for Python 3, upgrade dependencies.
- Follow homepage change.
- Move packaging repository to salsa.
- Drop nxt_filer, to be reintroduced later.
- Use machine readable debian/copyright file.
* Lower dependency to python3-bluez to Recommends.
* Update udev rules to match other LEGO team packages.
* Add documentation.
* Run included tests on build.
* Add upstream/metadata.
* Make tests and documentation optional at build.
* Add myself as uploader.
This is a package reintroduction.
The nxt-python package version 2.2.2-4 was removed as it depended on
Python 2, and pygtk2, see https://bugs.debian.org/954889. Also, upstream
development was not active anymore.
The new NXT-Python now use Python 3 and GTK 3.0 (only used for a filer
script) and is now actively maintained by me.
I plan to maintain it inside the Debian LEGO team.
About bugs #885467, #937175 and #773201: they were closed when the
package was removed, should I re-open them before the upload, or is it
handled at upload time?
I dropped the python-nxt-filer package as I do not find it particularely
useful, nor well finished.
About lintian report, I would like to have some advice on how to handle
it rather than going directly with an override:
I: nxt-python source: built-using-field-on-arch-all-package (in section for python3-nxt) Built-Using ${sphinxdoc:Built-Using}, [debian/control:34]
I think this is a bug in lintian as this is required by sphinx, see
https://bugs.debian.org/999785
P: python3-nxt: image-file-has-unexpected-name (is PNG) [usr/share/doc/python3-nxt/html/_static/favicon.ico]
Having a PNG inside a .ico is actually typical. Also see
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=717818#17
> I did not implement .ICO because it is, or has evolved into, a
> container format that can also contain PNG images.
P: nxt-python source: maintainer-manual-page [debian/man/nxt_push.1]
P: nxt-python source: maintainer-manual-page [debian/man/nxt_server.1]
P: nxt-python source: maintainer-manual-page [debian/man/nxt_test.1]
I am also the upstream maintainer, I plan to add them to
upstream package in the future. Maybe I should add an override
for this one.
X: python3-nxt: application-in-library-section python [usr/bin/nxt_push]
X: python3-nxt: application-in-library-section python [usr/bin/nxt_server]
X: python3-nxt: application-in-library-section python [usr/bin/nxt_test]
X: python3-nxt: library-package-name-for-application [usr/bin/nxt_push]
X: python3-nxt: library-package-name-for-application [usr/bin/nxt_server]
X: python3-nxt: library-package-name-for-application [usr/bin/nxt_test]
Not sure how to handle this one, is it acceptable to have some
script shipped inside the python module package? Should I make a
separated -utils package or an override.
nxt_push could be useful without nxt-python, but there are other
software doing the same thing already in other packages.
nxt_server is only useful with nxt-python, so it falls as an
helper.
nxt_test primary objective is to test connectivity with
nxt-python, so this is also a helper.
X: nxt-python source: debian-watch-does-not-check-openpgp-signature [debian/watch]
This is related to PyPI not encouraging PGP signature. Should I,
as the upstream author, make releases outside of PyPI?
X: nxt-python source: very-long-line-length-in-source-file 3559 > 512 [setup.py:20]
This is from generated upstream package, quoting the README
inside the setup.py.
Source can also be found on
https://salsa.debian.org/debian-lego-team/nxt-python, with candidate
code used to build the package on the "sponsor" branch.
Thanks for your reviews,
Regards,
--
Nicolas Schodet
Reply to: