Package: sponsorship-requests Severity: normal Dear mentors,
I am looking for a sponsor for my package "python-ajpy": * Package name : python-ajpy Version : 0.0.5-3 Upstream contact : Julien Legras <[email protected]> * URL : https://github.com/hypn0s/AJPy * License : BSD-3-Clause (debian/* : BSD-4-clause) * Vcs : https://salsa.debian.org/python-team/packages/python-ajpy Section : python The source builds the following binary package: python3-ajpy - Python module to craft AJP requests To access further information about this package, please visit the following URL: https://mentors.debian.net/package/python-ajpy/ Alternatively, you can download the package with 'dget' using this command: dget -x https://mentors.debian.net/debian/pool/main/p/python-ajpy/python-ajpy_0.0.5-3.dsc Changes since the last upload: python-ajpy (0.0.5-3) unstable; urgency=medium . * Adopt the package under the Debian Python Team umbrella (Closes: #1050246). * Add debian/salsa-ci.yml. * Add debian/upstream/metadata. * Bump Standards-Version to 4.7.4 and debhelper-compat to 14. * Drop the redundant Priority: optional field. The package was orphaned in August 2023 (#1050246). It is not widely installed - popcon 245, of which 33 votes - but patator depends on it, so it is a real part of the security tooling stack rather than a leaf nobody would miss. Maintainer moves from the QA Group to the Debian Python Team, which is where the packaging repository already lives, with myself in Uploaders. Of the normative changes across Policy 4.6.2 to 4.7.4, exactly one applies: 4.7.3 stopped recommending Priority in the source stanza, so it is dropped. The rest are not applicable to an arch:all pure-Python library in main - no shared libraries, no daemons requiring systemd units, nothing installed outside /usr/lib and /usr/share, no /usr/games. I checked that against the built .deb rather than assuming. QA, all against unstable: sbuild in a clean sid chroot succeeds; lintian 2.139.0 run inside the chroot reports no errors and no warnings; autopkgtest passes; piuparts passes install, upgrade and purge. Three things I want to be upfront about: * The autopkgtest is autodep8's generated python3 test and reports "PASS (superficial)" - it is an import check, not a real test of the AJP packet crafting. Upstream ships no test suite to hook up. Writing a genuine test would be a worthwhile follow-up, but it felt like scope beyond an adoption upload. * 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 here, and it is an I: tag rather than a W:. * Upstream has been quiet since 0.0.5 and the GitHub repository shows no recent activity. The package is small, stable and has a reverse dependency, so I judged adoption better than removal - but I am open to being told otherwise. This is my third package. The second, helpdev 0.7.1-7, was sponsored by Bastian Germann earlier this week; python-svg.path 7.1-1 is still open as #1143833. Regards, -- Dustin Kost
