Control: tags -1 moreinfo On Wed, 9 Apr 2025 17:43:33 +0200 Carl Keinath <carl.kein...@gmail.com> wrote:
> I am looking for a sponsor for my package python-pwdlib:
hi Carl,
* control:
+ build-deps on python3-mypy, python3-ruff appear unused?
+ documentation package has ${sphinxdoc:Depends} but doesn't
actually use sphinx.
+ python3-bcrypt and python3-argon2 are merely recommended,
although they provide core functionality of pwdlib; probably
should both be hard depends of the binary package even though
upstream code plays nice when either one is missing.
+ binary pkg python3-pwdlib set to architecture:any, but ships an
entirely arch-independent python module.
* tests: debian/tests/control runs the upstream testsuite in the
extracted source directory, which could cause the autopkgtest to
pass even in case the binary pkg were completely broken. It also
installs all build-deps, possibly hiding missing dependencies on
the binary pkg. Automation such as autopkgtest-pkg-pybuild does the
latter out of necessity, because it has no way to distinguish
between build-deps needed only for the testsuite and those imported
at runtime. For a human-written autopkgest on the other hand, the
maintainer can make that distinction, and should limit test deps to
the package being tested (python3-pwdlib) plus whatever is needed
specifically to support the testsuite (typically python3-all and
test frameworks such as pytest, sometimes also additional python
modules or utils).
Note that the salsa CI config allows one to set the release to
experimental (see [1]), although in the past some tests failed to
respect that setting (probably reprotest and/or piuparts). Still
better than everything failing over python3-argon2 being unavailable
in unstable.
[1]https://salsa.debian.org/gnome-team/shell-extensions/gnome-shell-extension-tiling-assistant/-/blob/f0731f83ef24a25abc614f17145e8d1f677c9724/debian/salsa-ci.yml
pgp2cnrMGOvNh.pgp
Description: OpenPGP digital signature
