hi Ileana, I took a look at pytest-fail-slow, up for sponsorship in the Python team.
Some repo issues:
* It appears tags were not pushed, as there's no tags at all in the
repo - not even for the imported upstream release - although the
typical gbp workflow would handle that.
* The upstream tarball produced by uscan differs from the
pristine-tar data. Are you making use of the standard tools for
importing new releases, e.g. 'gbp import-orig --pristine-tar
--uscan' or similar?
Then for the packaging itself (which is in pretty good shape):
* changelog: please leave the release at UNRELEASED, cf. team policy.
* control:
+ the binary pkg for a pytest plugin is commonly named
python3-pytest-<name-of-plugin>;
+ short description: Pytest plugin to [current description]?
* upstream/metadata missing.
* no autopkgtest? Should be a trivial yet *very* useful addition,
providing early warning for things like compatibility issues with
newer pytest releases before packages using the plugin start seeing
failures.
pgpn3NddLW6w2.pgp
Description: OpenPGP digital signature
