public inbox for git-commits@fedoraproject.org
help / color / mirror / Atom feed
From: Filipe Rosset <rosset.filipe@gmail.com>
To: git-commits@fedoraproject.org
Subject: [rpms/python-sport-activities-features] rawhide: Fix build with numpy-2.0
Date: Wed, 05 Aug 2026 22:54:01 GMT	[thread overview]
Message-ID: <178597044114.1.6439706747332771712.rpms-python-sport-activities-features-6c43f1fdc558@fedoraproject.org> (raw)

            A new commit has been pushed.

            Repo   : rpms/python-sport-activities-features
            Branch : rawhide
            Commit : 6c43f1fdc5583e0dbc59390ff8dc7144ce917843
            Author : Filipe Rosset <rosset.filipe@gmail.com>
            Date   : 2026-08-05T19:52:24-03:00
            Stats  : +24/-48 in 3 file(s)
            URL    : https://src.fedoraproject.org/rpms/python-sport-activities-features/c/6c43f1fdc5583e0dbc59390ff8dc7144ce917843?branch=rawhide

            Log:
            Fix build with numpy-2.0

Avoid load pyqt for tests

Resolves: rhbz#2439955 - python-sport-activities-features-0.5.4 is available
Resolves: rhbz#2485964 - F45FailsToInstall: python3-sport-activities-features
Resolves: rhbz#2504581 - python-sport-activities-features: FTBFS in Fedora rawhide/f45

---
diff --git a/.gitignore b/.gitignore
index b6f8b9c..7385ff9 100644
--- a/.gitignore
+++ b/.gitignore
@@ -1,43 +1 @@
-/sport-activities-features-0.1.2.tar.gz
-/sport-activities-features-0.2.0.tar.gz
-/sport-activities-features-0.2.1.tar.gz
-/sport-activities-features-0.2.2.tar.gz
-/sport-activities-features-0.2.3.tar.gz
-/sport-activities-features-0.2.4.tar.gz
-/sport-activities-features-0.2.5.tar.gz
-/sport-activities-features-0.2.6.tar.gz
-/sport-activities-features-0.2.7.tar.gz
-/sport-activities-features-0.2.8.tar.gz
-/sport-activities-features-0.2.9.tar.gz
-/sport-activities-features-0.2.10.tar.gz
-/sport-activities-features-0.2.11.tar.gz
-/sport-activities-features-0.2.12.tar.gz
-/sport-activities-features-0.2.14.tar.gz
-/sport-activities-features-0.2.15.tar.gz
-/sport-activities-features-0.2.16.tar.gz
-/sport-activities-features-0.2.18.tar.gz
-/sport-activities-features-0.3.0.tar.gz
-/sport-activities-features-0.3.1.tar.gz
-/sport-activities-features-0.3.2.tar.gz
-/sport-activities-features-0.3.5.tar.gz
-/sport-activities-features-0.3.6.tar.gz
-/sport-activities-features-0.3.7.tar.gz
-/sport-activities-features-0.3.7.1.tar.gz
-/sport-activities-features-0.3.7.2.tar.gz
-/sport-activities-features-0.3.8.tar.gz
-/sport-activities-features-0.3.10.tar.gz
-/sport-activities-features-0.3.11.tar.gz
-/sport-activities-features-0.3.12.tar.gz
-/sport-activities-features-0.3.14.tar.gz
-/sport-activities-features-0.3.15.tar.gz
-/sport-activities-features-0.3.15.1.tar.gz
-/sport-activities-features-0.3.16.tar.gz
-/sport-activities-features-0.3.17.tar.gz
-/sport-activities-features-0.3.18.tar.gz
-/sport-activities-features-0.4.0.tar.gz
-/sport-activities-features-0.4.1.tar.gz
-/sport-activities-features-0.4.2.tar.gz
-/sport-activities-features-0.5.0.tar.gz
-/sport-activities-features-0.5.1.tar.gz
-/sport-activities-features-0.5.2.tar.gz
-/sport-activities-features-0.5.4.tar.gz
+/sport-activities-features-*.tar.gz

diff --git a/numpy-2.0.patch b/numpy-2.0.patch
new file mode 100644
index 0000000..1faa4e8
--- /dev/null
+++ b/numpy-2.0.patch
@@ -0,0 +1,17 @@
+# Fix compatibility with NumPy 2.0 where np.cross is no longer allowed for 2D vectors
+# Ref: NumPy 2.0 release notes / deprecations
+--- a/sport_activities_features/area_identification.py
++++ b/sport_activities_features/area_identification.py
+@@ -102,9 +102,9 @@
+         v12 = np.array(p2 - p1)
+         v34 = np.array(p4 - p3)
+         v31 = np.array(p1 - p3)
+-        D = np.cross(v12, v34)
+-        A = np.cross(v34, v31)
+-        B = np.cross(v12, v31)
++        D = v12[0] * v34[1] - v12[1] * v34[0]
++        A = v34[0] * v31[1] - v34[1] * v31[0]
++        B = v12[0] * v31[1] - v12[1] * v31[0]
+ 
+         # If D == 0, the two line segments are parallel
+         if self.is_equal(D, 0):

diff --git a/python-sport-activities-features.spec b/python-sport-activities-features.spec
index c03afa6..ef62ae9 100644
--- a/python-sport-activities-features.spec
+++ b/python-sport-activities-features.spec
@@ -1,21 +1,21 @@
 %global pypi_name sport-activities-features
+%global forgeurl https://github.com/firefly-cpp/sport-activities-features
+Version:        0.5.4
+%forgemeta
 
 %bcond tests 1
 
 Name:           python-%{pypi_name}
-Version:        0.5.4
 Release:        %autorelease
 Summary:        A minimalistic toolbox for extracting features from sports activity files
 
-%global forgeurl https://github.com/firefly-cpp/sport-activities-features
-%global tag %{version}
-%forgemeta
-
 # SPDX
 License:        MIT
 URL:            %forgeurl
 Source:         %forgesource
 
+Patch:          numpy-2.0.patch
+
 BuildArch:      noarch
 BuildRequires:  python3-devel
 BuildRequires:  tomcli
@@ -84,6 +84,7 @@ done
 k="${k-}${k+ and }not test_overpy_node_manipulation"
 k="${k-}${k+ and }not test_weather"
 k="${k-}${k+ and }not test_data_analysis"
+export PYTEST_DISABLE_PLUGIN_AUTOLOAD=1
 %pytest -r fEs ${k:+-k "$k"}
 %else
 %pyproject_check_import

                 reply	other threads:[~2026-08-05 22:54 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=178597044114.1.6439706747332771712.rpms-python-sport-activities-features-6c43f1fdc558@fedoraproject.org \
    --to=rosset.filipe@gmail.com \
    --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