Package: sponsorship-requests Severity: normal Dear mentors,
I am looking for a sponsor for my package "helpdev": * Package name : helpdev Version : 0.7.1-7 Upstream contact : Daniel Cosmo Pizetta <[email protected]> * URL : https://gitlab.com/dpizetta/helpdev * License : MIT * Vcs : https://salsa.debian.org/python-team/packages/helpdev Section : python The source builds the following binary package: helpdev - Helper tool to get environment information To access further information about this package, please visit the following URL: https://mentors.debian.net/package/helpdev/ Alternatively, you can download the package with 'dget' using this command: dget -x https://mentors.debian.net/debian/pool/main/h/helpdev/helpdev_0.7.1-7.dsc Changes since the last upload: helpdev (0.7.1-7) unstable; urgency=medium . * Adopt the package under the Debian Python Team umbrella (Closes: #1067786). * Fix debian/watch, which had been failing since gitlab.com moved /tags to /-/tags: uscan concatenated the original and redirected bases into a pattern that matched nothing, and the archive links are now HTML-escaped JSON in a data attribute rather than plain hrefs. Switched to mode=git, which depends on neither. * Add a manual page for helpdev(1). * Add debian/salsa-ci.yml. * Bump Standards-Version to 4.7.4 and debhelper-compat to 14. * Drop the redundant Priority: optional field. The package had been orphaned since February 2024 (#1067786). I am a member of the Debian Python Team, so the packaging is already pushed to the team repository and its pipeline is green: https://salsa.debian.org/python-team/packages/helpdev https://salsa.debian.org/python-team/packages/helpdev/-/pipelines/1147394 The substantive change is the watch file. It had been broken in two ways at once, so uscan reported "no matching files for watch source" and the package had effectively been invisible to upstream-version tracking. mode=git avoids the HTML scraping entirely; uscan now correctly resolves 0.7.1. The manual page is new and written from helpdev/__main__.py rather than the README, so the options and defaults match what argparse actually accepts. It documents the PEI/PED/PEAD markers that appear against every option in --help but are only explained in the README, and it carries a PRIVACY section: --all-for-sure includes --path and --scope, which expose home directory paths and the running scope, and upstream explicitly cautions about sharing that output. I intend to offer the page upstream. 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. Two things I did not change, deliberately: * package-installs-legacy-python-egg-info. Upstream ships only setup.py and setup.cfg with no pyproject.toml, so switching to pybuild-plugin-pyproject would mean patching upstream. That felt too invasive for an adoption upload, and it is an I: tag rather than a W:. * python3-pip remains a build dependency. It is not referenced in debian/rules and looks removable, but helpdev shells out to "pip list" in helpdev/__init__.py and the test suite exercises that path; removing it fails the build. Worth noting, since it is a plausible thing for a future reviewer to want to drop. One thing I would value a second opinion on: helpdev calls pip at runtime but the binary package does not depend on python3-pip. That looks like a genuine missing dependency to me, but I did not want to add a Depends in the same upload as the adoption without a second pair of eyes. This is my second package. Review is as welcome as sponsorship. Regards, -- Dustin Kost
