@@ -1,4 +1,4 @@
-From 5cb7316128845e3da1ce1618a42b2e3222b59ba9 Mon Sep 17 00:00:00 2001
+From 372ec5d5fb94fa029ee015152491b8b88b099b2a Mon Sep 17 00:00:00 2001
From: Alexander Kanavin <alex.kanavin@gmail.com>
Date: Thu, 10 Dec 2015 13:20:30 +0200
Subject: [PATCH] Don't search /usr and so on for libraries by default to
@@ -1,11 +1,11 @@
-From c40218577305f5953ef63d943c26a27c5a931770 Mon Sep 17 00:00:00 2001
+From 2635c925d507d5a6c3b0af10a564ca8f9252981c Mon Sep 17 00:00:00 2001
From: Ross Burton <ross.burton@arm.com>
Date: Wed, 21 Jan 2026 14:12:36 +0000
Subject: [PATCH] Add sysroot to pkgconfig libdir
When Meson uses pkg-config to introspect the Python install it resets PKG_CONFIG_PATH
and PKG_CONFIG_LIBDIR. However, when it writes to PKG_CONFIG_LIBDIR it uses the
-_target_ library directory without prefixing this with the sysroot, which breaks
+_target_ library directory without prefixing this with the sysroot, which breaks
the build if _LIBDIR is the primary search path.
This has been fixed in Meson since 1.10.0[1] but numpy has a vendored fork of Meson
@@ -1,4 +1,4 @@
-From 6fd79cbe7ae9f0a7a5fc4e5cd6c5c3da9ea09815 Mon Sep 17 00:00:00 2001
+From 8aca0d4aa45561bea3d86bc252d642c9c02e5d70 Mon Sep 17 00:00:00 2001
From: Richard Purdie <richard.purdie@linuxfoundation.org>
Date: Fri, 29 Sep 2023 22:53:24 +0100
Subject: [PATCH] This regex decides whether to use O3 opimisation on numpy or
similarity index 97%
rename from meta/recipes-devtools/python/python3-numpy_2.4.3.bb
rename to meta/recipes-devtools/python/python3-numpy_2.4.4.bb
@@ -13,7 +13,7 @@ SRC_URI = "${GITHUB_BASE_URI}/download/v${PV}/${SRCNAME}-${PV}.tar.gz \
file://run-ptest \
file://0001-python-sysroot.patch \
"
-SRC_URI[sha256sum] = "483a201202b73495f00dbc83796c6ae63137a9bdade074f7648b3e32613412dd"
+SRC_URI[sha256sum] = "2d390634c5182175533585cc89f3608a4682ccb173cc9bb940b2881c8d6f8fa0"
GITHUB_BASE_URI = "https://github.com/numpy/numpy/releases"
UPSTREAM_CHECK_REGEX = "releases/tag/v?(?P<pver>\d+(\.\d+)+)$"
Hello, this email is a notification from the Auto Upgrade Helper that the automatic attempt to upgrade the recipe(s) *python3-numpy* to *2.4.4* has Succeeded. Next steps: - apply the patch: git am 0001-python3-numpy-upgrade-2.4.3-2.4.4.patch - check the changes to upstream patches and summarize them in the commit message, - compile an image that contains the package - perform some basic sanity tests - amend the patch and sign it off: git commit -s --reset-author --amend - send it to the appropriate mailing list Alternatively, if you believe the recipe should not be upgraded at this time, you can fill RECIPE_NO_UPDATE_REASON in respective recipe file so that automatic upgrades would no longer be attempted. Please review the attached files for further information and build/update failures. Any problem please file a bug at https://bugzilla.yoctoproject.org/enter_bug.cgi?product=Automated%20Update%20Handler Regards, The Upgrade Helper -- >8 -- From 3ca154e2f809b500ebc711a1eafa952dac857391 Mon Sep 17 00:00:00 2001 From: Upgrade Helper <auh@yoctoproject.org> Date: Wed, 1 Apr 2026 10:03:58 +0000 Subject: [PATCH] python3-numpy: upgrade 2.4.3 -> 2.4.4 --- ...Don-t-search-usr-and-so-on-for-libraries-by-default-.patch | 2 +- .../python/python3-numpy/0001-python-sysroot.patch | 4 ++-- .../python/python3-numpy/fix_reproducibility.patch | 2 +- .../python/{python3-numpy_2.4.3.bb => python3-numpy_2.4.4.bb} | 2 +- 4 files changed, 5 insertions(+), 5 deletions(-) rename meta/recipes-devtools/python/{python3-numpy_2.4.3.bb => python3-numpy_2.4.4.bb} (97%)