Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]


Groups > linux.debian.maint.python > #14727

review for pytest-fail-slow/0.3.0-1

Path csiph.com!aioe.org!bofh.it!news.nic.it!robomod
From Jeroen Ploemen <jcfp@debian.org>
Newsgroups linux.debian.maint.python
Subject review for pytest-fail-slow/0.3.0-1
Date Wed, 14 Dec 2022 14:00:01 +0100
Message-ID <FCzwB-aBJg-1@gated-at.bofh.it> (permalink)
X-Mailbox-Line From debian-python-request@lists.debian.org Wed Dec 14 12:52:04 2022
Old-Return-Path <jcfp@debian.org>
X-Amavis-Spam-Status No, score=-115.024 tagged_above=-10000 required=5.3 tests=[BAYES_00=-2, DKIMWL_WL_HIGH=-0.515, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, LDO_WHITELIST=-5, PGPSIGNATURE=-5, RCVD_IN_DNSWL_MED=-2.3, UNPARSEABLE_RELAY=0.001, USER_IN_DKIM_WELCOMELIST=-0.01, USER_IN_DKIM_WHITELIST=-100] autolearn=ham autolearn_force=no
X-Mailer Claws Mail 4.1.1 (GTK 3.24.20; x86_64-pc-linux-gnu)
MIME-Version 1.0
Content-Type multipart/signed; boundary="Sig_/dHeXCKgJtgNuINdOx43.lhm"; protocol="application/pgp-signature"; micalg=pgp-sha512
X-Debian-User jcfp
X-Mailing-List <debian-python@lists.debian.org> archive/latest/20593
List-ID <debian-python.lists.debian.org>
List-URL <https://lists.debian.org/debian-python/>
List-Archive https://lists.debian.org/msgid-search/20221214135120.3ea97dce@debian.org
Approved robomod@news.nic.it
Lines 54
Organization linux.* mail to news gateway
Sender robomod@news.nic.it
X-Original-Cc debian-python@lists.debian.org
X-Original-Date Wed, 14 Dec 2022 13:51:20 +0100
X-Original-Message-ID <20221214135120.3ea97dce@debian.org>
Xref csiph.com linux.debian.maint.python:14727

Show key headers only | View raw


[Multipart message — attachments visible in raw view] - view raw

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.

Back to linux.debian.maint.python | Previous | Next — Next in thread | Find similar | Unroll thread


Thread

review for pytest-fail-slow/0.3.0-1 Jeroen Ploemen <jcfp@debian.org> - 2022-12-14 14:00 +0100
  Re: review for pytest-fail-slow/0.3.0-1 Ileana Dumitrescu <ileanadumitrescu95@gmail.com> - 2022-12-21 18:10 +0100

csiph-web