public inbox for git-commits@fedoraproject.org
help / color / mirror / Atom feed
From: Benjamin A. Beasley <code@musicinmybrain.net>
To: git-commits@fedoraproject.org
Subject: [rpms/python-scooby] f44: Use long pyproject and pytest options
Date: Fri, 11 Sep 2026 12:15:34 GMT	[thread overview]
Message-ID: <178912893481.1.821572834965261705.rpms-python-scooby-d80d78b4fc56@fedoraproject.org> (raw)

A new commit has been pushed.

Repo   : rpms/python-scooby
Branch : f44
Commit : d80d78b4fc569e0978b9f2ed1f7f05c901fa75d2
Author : Benjamin A. Beasley <code@musicinmybrain.net>
Date   : 2026-05-16T22:13:54+01:00
Stats  : +4/-4 in 1 file(s)
URL    : https://src.fedoraproject.org/rpms/python-scooby/c/d80d78b4fc569e0978b9f2ed1f7f05c901fa75d2?branch=f44

Log:
Use long pyproject and pytest options

---
diff --git a/python-scooby.spec b/python-scooby.spec
index 215853b..43bbcae 100644
--- a/python-scooby.spec
+++ b/python-scooby.spec
@@ -11,13 +11,13 @@ Source0:        %{url}/archive/v%{version}/scooby-%{version}.tar.gz
 # Man page hand-written for Fedora in groff_man(7) format based on --help
 Source1:        scooby.1
 
-BuildSystem:            pyproject
+BuildSystem:    pyproject
 # We cannot package (nor generate BR’s from) the “cpu” extra because it
 # requires python3dist(mkl), which is proprietary software.
 %if %{with tests}
-BuildOption(generate_buildrequires): -g test
+BuildOption(generate_buildrequires): --dependency-groups test
 %endif
-BuildOption(install):   -l scooby
+BuildOption(install): --assert-license scooby
 
 BuildArch:      noarch
 
@@ -83,7 +83,7 @@ k="${k-}${k+ and }not test_import_os_error"
 # Import performance test may fail flakily or on slower hardware
 k="${k-}${k+ and }not test_import_time"
 
-%pytest -k "${k-}" -v
+%pytest -k "${k-}" --verbose
 %endif
 
 

                 reply	other threads:[~2026-09-11 12:15 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=178912893481.1.821572834965261705.rpms-python-scooby-d80d78b4fc56@fedoraproject.org \
    --to=code@musicinmybrain.net \
    --cc=git-commits@fedoraproject.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox