public inbox for git-commits@fedoraproject.org
help / color / mirror / Atom feed
To: git-commits@fedoraproject.org
Subject: [rpms/fedpkg] 1.48-1: Drop nosetests for Python3
Date: Mon, 10 Aug 2026 21:46:00 GMT	[thread overview]
Message-ID: <178639836028.1.5624606507042542826.rpms-fedpkg-94c757a8e1c8@fedoraproject.org> (raw)

            A new commit has been pushed.

            Repo   : rpms/fedpkg
            Branch : 1.48-1
            Commit : 94c757a8e1c848f36e31e892c74edf707e24e7d5
            Author : Ondřej Nosek <onosek@redhat.com>
            Date   : 2021-12-14T17:58:19+00:00
            Stats  : +33/-3 in 2 file(s)
            URL    : https://src.fedoraproject.org/rpms/fedpkg/c/94c757a8e1c848f36e31e892c74edf707e24e7d5?branch=1.48-1

            Log:
            Drop nosetests for Python3

and disable pytest coverage during build

Signed-off-by: Ondřej Nosek <onosek@redhat.com>

---
diff --git a/0003-Remove-pytest-coverage-execution.patch b/0003-Remove-pytest-coverage-execution.patch
new file mode 100644
index 0000000..446c5fa
--- /dev/null
+++ b/0003-Remove-pytest-coverage-execution.patch
@@ -0,0 +1,25 @@
+From 4e22dfa592ca7a39cbd90c9a02a2a536658cb027 Mon Sep 17 00:00:00 2001
+From: Ondrej Nosek <onosek@redhat.com>
+Date: Tue, 14 Dec 2021 18:55:30 +0100
+Subject: [PATCH] Remove pytest coverage execution
+
+Signed-off-by: Ondrej Nosek <onosek@redhat.com>
+---
+ setup.cfg | 1 -
+ 1 file changed, 1 deletion(-)
+
+diff --git a/setup.cfg b/setup.cfg
+index 133a7fa..8e0661e 100644
+--- a/setup.cfg
++++ b/setup.cfg
+@@ -6,7 +6,6 @@ formats = bztar
+ 
+ [tool:pytest]
+ cover-package = fedpkg
+-addopts = --cov=fedpkg
+ testpaths = test
+ 
+ [flake8]
+-- 
+2.31.1
+

diff --git a/fedpkg.spec b/fedpkg.spec
index 7972ebe..4654376 100644
--- a/fedpkg.spec
+++ b/fedpkg.spec
@@ -5,7 +5,7 @@
 
 Name:           fedpkg
 Version:        1.41
-Release:        2%{?dist}
+Release:        3%{?dist}
 Summary:        Fedora utility for working with dist-git
 
 License:        GPLv2+
@@ -16,6 +16,7 @@ BuildArch:      noarch
 Patch1:         0001-Do-not-use-pytest-related-dependencies-temporarily.patch
 # https://pagure.io/fedpkg/pull-request/453
 Patch2:         0002-Add-support-for-epel9-next.patch
+Patch3:         0003-Remove-pytest-coverage-execution.patch
 
 # RHEL7 is currently the only release that is built for Python 2.
 %if 0%{?fedora} || 0%{?rhel} > 7
@@ -68,7 +69,7 @@ BuildRequires:  python3-distro
 BuildRequires:  python3-fedora
 # For testing
 BuildRequires:  python3-mock
-BuildRequires:  python3-nose
+BuildRequires:  python3-pytest
 BuildRequires:  python3-setuptools
 BuildRequires:  python3-bugzilla
 BuildRequires:  python3-freezegun
@@ -117,7 +118,7 @@ mv %{buildroot}%{compdir}/fedpkg.bash %{buildroot}%{compdir}/fedpkg
 %if %{with python2}
 %{__python2} -m nose
 %else
-%{__python3} -m nose
+%pytest
 %endif
 
 
@@ -145,6 +146,10 @@ mv %{buildroot}%{compdir}/fedpkg.bash %{buildroot}%{compdir}/fedpkg
 
 
 %changelog
+* Tue Dec 14 2021 Ondřej Nosek <onosek@redhat.com> - 1.41-3
+- drop nosetests for Python3
+- disable pytest coverage during build
+
 * Mon Nov 08 2021 Carl George <carl@george.computer> - 1.41-2
 - Allow branch requests for epel9-next
 

                 reply	other threads:[~2026-08-10 21:46 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=178639836028.1.5624606507042542826.rpms-fedpkg-94c757a8e1c8@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