Dear mentors,
I am looking for a sponsor for my package "python-rply":
* Package name : python-rply
Version : 0.7.8-4
Upstream contact : https://github.com/alex/rply/issues
* URL : https://github.com/alex/rply
* License : BSD-3-clause (debian/* : GPL-3+)
* Vcs : https://salsa.debian.org/python-team/packages/python-rply
Section : python
The source builds the following binary package:
python3-rply - pure Python based parser that also works with RPython (Python 3)
To access further information about this package, please visit the following URL:
https://mentors.debian.net/package/python-rply/
Alternatively, you can download the package with 'dget' using this command:
dget -x https://mentors.debian.net/debian/pool/main/p/python-rply/python-rply_0.7.8-4.dsc
Changes since the last upload:
python-rply (0.7.8-4) unstable; urgency=medium
.
* Adopt the package under the Debian Python Team umbrella
(Closes: #1093669).
* Add myself to Uploaders.
* Bump debhelper-compat to 14 and Standards-Version to 4.7.4.
* Drop the redundant Priority: optional and Rules-Requires-Root: no
fields.
* Rewrite debian/watch using the version 5 PyPI template.
* Drop debian/upstream/signing-key.asc: PyPI publishes no OpenPGP
signatures and the upstream git tags are not signed, so nothing
can verify the download.
* Correct the spelling of David Beazley's name in the description.
* Add debian/salsa-ci.yml.
The package was orphaned in January 2025 (#1093669). It is not a leaf:
i18nspector, python3-rnc2rng and python3-baron all depend on it, and
i18nspector is itself part of the Debian i18n QA toolchain.
Maintainer stays as the Debian Python Team, which is where the packaging
repository already lives. The package simply had nobody in Uploaders, which
lintian reports as no-human-maintainers and which is what failed the Salsa CI
lintian job; I have added myself.
Three changes are worth explaining rather than just listing:
* debian/upstream/signing-key.asc is removed rather than wired up. It was
producing both debian-watch-could-verify-download and
orig-tarball-missing-upstream-signature, and verification cannot actually
be enabled here: PyPI reports no OpenPGP signature for any rply release
ever published, having dropped signature support in 2023, and the
upstream git tags are lightweight rather than annotated, so pgpmode=gittag
has nothing to check either. I would rather delete a key that cannot
verify anything than leave it in place implying that it does.
* debian/watch moves to the version 5 PyPI template. The template supplies
exactly what the old v3 file spelled out by hand - the pypi.debian.net
base, plain searchmode, and uversionmangle s/(rc|a|b|c)/~$1/ - and it
records pgpmode=none explicitly, which is the machine-readable form of the
point above. uscan reports the package up to date at 0.7.8.
* The description misspelled the author of PLY as "David Bazzley". Upstream's
README has it as David Beazley. Corrected.
QA, all against unstable: sbuild in a clean sid chroot succeeds; lintian
2.139.0 run inside that chroot reports no errors, no warnings and no pedantic
tags; autopkgtest passes; piuparts passes install, upgrade and purge. The
orig.tar.gz is byte-identical to the copy already in the archive, which I
checked against deb.debian.org rather than assuming.
Salsa CI, all jobs green:
https://salsa.debian.org/python-team/packages/python-rply/-/pipelines/1149701
Two things I want to be upfront about:
* The autopkgtest is autodep8's generated python3 test and reports
"PASS (superficial)" - it imports the module and stops there. Upstream
does ship a real test suite, but MANIFEST.in excludes it from the sdist,
so it is not in the tarball at all. Switching debian/watch to mode=git
would pull the tests in and let me wire up a genuine autopkgtest. I did
not want to change upstream tarball provenance in the same upload as the
adoption, but I am happy to do it as a follow-up, or in this upload
instead if you would rather see it done once.
* package-installs-legacy-python-egg-info remains. Upstream ships only
setup.py and setup.cfg with no pyproject.toml, so moving to
pybuild-plugin-pyproject would mean patching upstream. That seemed too
invasive for an adoption, and it is an I: tag rather than a W:.
Upstream has been quiet since 0.7.8 in January 2021, and the last commit to
the GitHub repository was January 2023. The repository is not archived and
the package is small, stable and has three reverse dependencies, so I judged
adoption better than removal - but I am open to being told otherwise.
This is my fourth package. helpdev 0.7.1-7 is in unstable; python-svg.path
7.1-1 (#1143833) and python-ajpy 0.0.5-3 (#1144362) are still open.
Regards,
--
Dustin Kost