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-keyring] rawhide: Better BuildOption formatting
Date: Fri, 11 Sep 2026 09:27:06 GMT [thread overview]
Message-ID: <178911882653.1.14172094138691039966.rpms-python-keyring-8621b364d144@fedoraproject.org> (raw)
A new commit has been pushed.
Repo : rpms/python-keyring
Branch : rawhide
Commit : 8621b364d144b9f84a31893d4db25eff40281620
Author : Benjamin A. Beasley <code@musicinmybrain.net>
Date : 2026-09-11T10:25:03+01:00
Stats : +5/-5 in 1 file(s)
URL : https://src.fedoraproject.org/rpms/python-keyring/c/8621b364d144b9f84a31893d4db25eff40281620?branch=rawhide
Log:
Better BuildOption formatting
---
diff --git a/python-keyring.spec b/python-keyring.spec
index 096f9a4..32b2fc5 100644
--- a/python-keyring.spec
+++ b/python-keyring.spec
@@ -15,13 +15,13 @@ BuildSystem: pyproject
BuildOption(generate_buildrequires): --extras %{?with_tests:test,}completion
BuildOption(install): --assert-license keyring
# - keyring.backends.macOS does not import on this platform
+BuildOption(check): --exclude 'keyring.backends.macOS*'
+%if %{without tests}
# - keyring.devpi_client and keyring.testing are test hooks that require pluggy
# and/or pytest; we can import them only if the test dependencies are present
-BuildOption(check): %{shrink:
- --exclude 'keyring.backends.macOS*'
- %{?!with_tests:--exclude 'keyring.devpi_client'}
- %{?!with_tests:--exclude 'keyring.testing*'}
- }
+BuildOption(check): --exclude 'keyring.devpi_client'
+BuildOption(check): --exclude 'keyring.testing*'
+%endif
BuildArch: noarch
reply other threads:[~2026-09-11 9:27 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=178911882653.1.14172094138691039966.rpms-python-keyring-8621b364d144@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