public inbox for git-commits@fedoraproject.org
help / color / mirror / Atom feed
To: git-commits@fedoraproject.org
Subject: [rpms/python-asyncssh] f44: Properly filter out test dependency on uvloop and python-pkcs11
Date: Sat, 11 Jul 2026 21:33:12 GMT	[thread overview]
Message-ID: <178380559257.1.960645605051171669.rpms-python-asyncssh-bbda2ed3268d@fedoraproject.org> (raw)

            A new commit has been pushed.

            Repo   : rpms/python-asyncssh
            Branch : f44
            Commit : bbda2ed3268d6d0b861a908a7809a086b4f8875f
            Author : Miro Hrončok <miro@hroncok.cz>
            Date   : 2026-05-06T12:34:36+02:00
            Stats  : +2/-1 in 1 file(s)
            URL    : https://src.fedoraproject.org/rpms/python-asyncssh/c/bbda2ed3268d6d0b861a908a7809a086b4f8875f?branch=f44

            Log:
            Properly filter out test dependency on uvloop and python-pkcs11

The dependency is specified in tox.ini as "linux,darwin: uvloop>=0.9.1" --
older tox did not understand it, so ti was silently skipped.
tox 4.53.1 recognises it, making the build fail with:

    Handling uvloop>=0.9.1 from tox --print-deps-only: py314
    Requirement not satisfied: uvloop>=0.9.1
    ...
    No match for argument: python3dist(uvloop) >= 0.9.1

Same for "linux,darwin: python-pkcs11>=0.7.0".

---
diff --git a/python-asyncssh.spec b/python-asyncssh.spec
index 3be8250..3ce140b 100644
--- a/python-asyncssh.spec
+++ b/python-asyncssh.spec
@@ -54,7 +54,8 @@ Summary:        %{summary}
 %autosetup -p1 -n %{srcname}-%{version}
 
 # remove superfluous build dependencies
-sed '/pytest-cov/d' tox.ini -i
+sed '/pytest-cov/d' tox.ini -i  # coverage not desired
+sed -E '/(uvloop|python-pkcs11)/d' tox.ini -i  # not available, tests skipped when missing
 
 
 %generate_buildrequires

                 reply	other threads:[~2026-07-11 21:33 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=178380559257.1.960645605051171669.rpms-python-asyncssh-bbda2ed3268d@fedoraproject.org \
    --to=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