From patchwork Sun Oct 11 05:21:45 2026 Content-Type: text/plain; charset="utf-8" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit X-Patchwork-Submitter: auh@yoctoproject.org X-Patchwork-Id: 100293 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on aws-us-west-2-korg-lkml-1.web.codeaurora.org Received: from aws-us-west-2-korg-lkml-1.web.codeaurora.org (localhost.localdomain [127.0.0.1]) by smtp.lore.kernel.org (Postfix) with ESMTP id 0CF5CCA9EC9 for ; Sun, 11 Oct 2026 05:21:55 +0000 (UTC) Received: from a27-23.smtp-out.us-west-2.amazonses.com (a27-23.smtp-out.us-west-2.amazonses.com [54.240.27.23]) by mx.groups.io with SMTP id smtpd.msgproc01-g2.22059.1791696106262577975 for ; Sat, 10 Oct 2026 22:21:46 -0700 Authentication-Results: mx.groups.io; dkim=pass header.i=@yoctoproject.org header.s=lvjh2tk576v2ro5mi6k4dt3mc6wpqbky header.b=OyhF7uzA; dkim=pass header.i=@amazonses.com header.s=hsbnp7p3ensaochzwyq5wwmceodymuwv header.b=QX910MlP; spf=pass (domain: us-west-2.amazonses.com, ip: 54.240.27.23, mailfrom: 010101a12968ef3e-91d6bfd4-1a3a-4ae0-937f-c3fd6204d975-000000@us-west-2.amazonses.com) DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/simple; s=lvjh2tk576v2ro5mi6k4dt3mc6wpqbky; d=yoctoproject.org; t=1791696105; h=Content-Type:MIME-Version:From:To:Cc:Subject:Message-Id:Date; bh=TEGoscFEth6O5EMQjqRmlgXM0VgjxCY4EZ481PGG9OE=; b=OyhF7uzAdEo1Q8GyDHN25QGhPs/VwDWcf1f/dlM3UuOYGY1t7+YgDB5zXw0f3crd 6YvH+ouv8UY5g1SIzamOv/sUogsczoF60lCt/v7m04B56zq650DeQoLIj8KSEIFfo36 /LL65v9j37SevFiWUnur6OvyTbnVivdsCxcIL3XM= DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/simple; s=hsbnp7p3ensaochzwyq5wwmceodymuwv; d=amazonses.com; t=1791696105; h=Content-Type:MIME-Version:From:To:Cc:Subject:Message-Id:Date:Feedback-ID; bh=TEGoscFEth6O5EMQjqRmlgXM0VgjxCY4EZ481PGG9OE=; b=QX910MlPA7uvz2Xdd8HhwJVy+mm0AEcRIDd90tOMt25Mky5qdts9m/J41zKSYQud JiNF12JMGl9BAQEkLacZj+tS+iJvwwdtua1VVrHqb4vuWuSED9BuHqrGckQygey4bYM HSUCJpoJ0cg9BxOJvG9Le+UE9dLFyVVJVnlNNFnc= MIME-Version: 1.0 From: auh@yoctoproject.org To: Trevor Gamblin Cc: openembedded-core@lists.openembedded.org Subject: [AUH] python3-numpy: upgrading to 2.5.4 SUCCEEDED Message-ID: <010101a12968ef3e-91d6bfd4-1a3a-4ae0-937f-c3fd6204d975-000000@us-west-2.amazonses.com> Date: Sun, 11 Oct 2026 05:21:45 +0000 Feedback-ID: ::1.us-west-2.9np3MYPs3fEaOBysGKSlUD4KtcmPijcmS9Az2Hwf7iQ=:AmazonSES X-SES-Outgoing: 2026.10.11-54.240.27.23 List-Id: X-Webhook-Received: from 45-33-107-173.ip.linodeusercontent.com [45.33.107.173] by aws-us-west-2-korg-lkml-1.web.codeaurora.org with HTTPS for ; Sun, 11 Oct 2026 05:21:55 -0000 X-Groupsio-URL: https://lists.openembedded.org/g/openembedded-core/message/247508 Hello, this email is a notification from the Auto Upgrade Helper that the automatic attempt to upgrade the recipe(s) *python3-numpy* to *2.5.4* has Succeeded. Next steps: - apply the patch: git am 0001-python3-numpy-upgrade-2.5.3-2.5.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 51bae7cbe369a9f6a105f12218df181d6dbba9fa Mon Sep 17 00:00:00 2001 From: Upgrade Helper Date: Sun, 11 Oct 2026 05:17:42 +0000 Subject: [PATCH] python3-numpy: upgrade 2.5.3 -> 2.5.4 Contributors ============ A total of 9 people contributed to this release. People with a "+" by their names contributed a patch for the first time. Pull requests merged ==================== A total of 17 pull requests were merged for this release. .. currentmodule:: numpy ========================= NumPy 2.5.4 Release Notes ========================= *Released on 2026-10-10.* NumPy 2.5.4 is a patch release that fixes bugs discovered after the 2.5.3 release. Highlights are: - Many typing fixes and improvements, - A workaround for the MSVC 19.51 bug, see below. This release supports Python versions 3.12-3.15. Improvements ============ - ``numpy.linalg.svd`` and ``numpy.linalg.lstsq`` now raise for inputs containing infinities instead of returning garbage results. - Fixed hangs in ``numpy.linalg.svd`` and ``numpy.linalg.lstsq`` for certain inputs containing infinities for recent versions of some LAPACK implementations. - ``numpy.linalg.cond`` now handles non-finite inputs more consistently. (`gh-32593 < >`__) StringDType hashing with NaN sentinels -------------------------------------- ``StringDType`` instances with equivalent floating-point NaN sentinels now have equal hashes. Previously, distinct NaN objects could produce equal dtype instances with different hashes, causing dictionary lookups and set deduplication to fail. (`gh-32563 < >`__) Changes ======= ``MaskedArray`` resets a fill_value that cannot be represented in a new dtype ----------------------------------------------------------------------------- A fill_value copied from a source array is now reset to the default fill_value for the new dtype when it cannot be represented in that dtype. Previously the copied value could be stale: ufuncs that change dtype left the result holding a fill_value typed for the old dtype, which raised a ``TypeError`` only when something later validated it (such as ``.view()``), and a floating point fill_value that overflows an integer dtype was kept as an out-of-range value together with a ``RuntimeWarning``. Both now fall back to the default, including when a masked array is passed to ``MaskedArray`` with a different ``dtype``. A fill_value given explicitly by the user is still validated and raises as before. This can now raise a ``ComplexWarning`` if the fill_value is complex and the new dtype is real. (`gh-32508 < >`__) (`gh-32562 < >`__) Contributors ============ A total of 9 people contributed to this release. People with a "+" by their names contributed a patch for the first time. Pull requests merged ==================== A total of 17 pull requests were merged for this release. --- title: Release 1.11.0 short-description: Release notes for 1.11.0 # New features Meson 1.11.0 was released on 13 April 2026 ## BuildTarget(install_dir) length > 1 replaced with keywords Build targets previously supported (with limited documentation) passing an array of more than one element to `install_dir:` (except in some wrappers), and would map these additional `install_dir`s to extra outputs. This was only used by Vala, and separate explicit keyword arguments are now available that provide the same functionality. Code like this: ```meson library( 'foo', 'foo.vala', install : true, install_dir : [true, get_option('includedir') / 'foo', true], ) ``` should now be written as the much clearer: ```meson library( 'foo', 'foo.vala', install : true, install_vala_header : get_option('includedir') / 'foo', install_vala_vapi : true, ) ``` Note that the default is `false` for the Vala extra outputs. ## Cargo workspace object Meson is now able to parse the toplevel `Cargo.toml` file of the project when the `workspace()` method of the Rust module is called. This guarantees that features are resolved according to what is in the `Cargo.toml` file, and in fact enables configuration of features for the build. The returned object allows retrieving features and dependencies for Cargo subprojects, and contains methods to build targets declared in `Cargo.toml` files. While Cargo subprojects remain experimental, the Meson project will try to keep the workspace object reasonably backwards-compatible. ## Cython no longer requires explicitly enabling C or C++ This only provides these languages as an implementation detail of Cython, so native C/C++ targets cannot be compiled. ## Deduplication of OpenMP linker arguments Meson now deduplicates linker arguments `-fopenmp` and `-qopenmp`. ## `meson dist` now accepts `-j`/`--num-processes` `meson dist` now supports a `-j`/`--num-processes` flag to control the number of parallel processes used during the distribution check (compilation and testing of the generated package). The `MESON_NUM_PROCESSES` environment variable is also honored, consistent with other Meson commands. ## Deprecate `should_fail` and rename it to `expected_fail`, also introduce `expected_exitcode` In 1.11.0 `should_fail` has been renamed to `expected_fail`. Before 1.11.0, [Changelog truncated as it exceeds 5000 characters; the full changelog can be found in an attachment to the AUH email] --- .../python/{python3-numpy_2.5.3.bb => python3-numpy_2.5.4.bb} | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) rename meta/recipes-devtools/python/{python3-numpy_2.5.3.bb => python3-numpy_2.5.4.bb} (97%) diff --git a/meta/recipes-devtools/python/python3-numpy_2.5.3.bb b/meta/recipes-devtools/python/python3-numpy_2.5.4.bb similarity index 97% rename from meta/recipes-devtools/python/python3-numpy_2.5.3.bb rename to meta/recipes-devtools/python/python3-numpy_2.5.4.bb index 338bdd2bbd..93aa356db1 100644 --- a/meta/recipes-devtools/python/python3-numpy_2.5.3.bb +++ b/meta/recipes-devtools/python/python3-numpy_2.5.4.bb @@ -10,7 +10,7 @@ SRCNAME = "numpy" SRC_URI = "${GITHUB_BASE_URI}/download/v${PV}/${SRCNAME}-${PV}.tar.gz \ file://run-ptest \ " -SRC_URI[sha256sum] = "df2d5874ff183595a4ba404edd04f6bd9b5505c1d7708573f6a6c17489a67563" +SRC_URI[sha256sum] = "9a94cf751c9ad8ebaa835bcd3d40dacf8534ad086b88c38029b65123c7999d2a" GITHUB_BASE_URI = "https://github.com/numpy/numpy/releases" UPSTREAM_CHECK_REGEX = "releases/tag/v?(?P\d+(\.\d+)+)$"