python3-git: upgrade 3.1.61 -> 3.1.62
PATCH 1/2 python3-git: upgrade 3.1.61 -> 3.1.62
Source: doc/source/changes.rst
3.1.62
======
Security fixes for
* https://github.com/gitpython-developers/GitPython/security/advisories/GHSA-59cr-6r3x-644w
https://github.com/gitpython-developers/GitPython/releases/tag/3.1.62
---
.../python/{python3-git_3.1.61.bb => python3-git_3.1.62.bb} | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
rename meta/recipes-devtools/python/{python3-git_3.1.61.bb => python3-git_3.1.62.bb} (92%)meta/recipes-devtools/python/python3-git_3.1.62.bb renamed from meta/recipes-devtools/python/python3-git_3.1.61.bb +1 -1
@@ -14,7 +14,7 @@ CVE_PRODUCT = "gitpython_project:gitpython" inherit pypi python_setuptools_build_meta -SRC_URI[sha256sum] = "f51c24d8c0f733a195447385f5774a5dfe8767f5acfd7994a33755644c6ecc95" +SRC_URI[sha256sum] = "1791de66309bc0c7cfca40bf8d2e3de7ca091cbf94e6051be1ad0722c61062af" DEPENDS += " python3-gitdb"
PATCH 2/2 python3-numpy: upgrade 2.5.2 -> 2.5.3
The NumPy 2.5.3 is a patch release that fixes bugs discovered after the 2.5.2 release. Apart from the usual bug and maintenance work, there are a number of StringDType related fixes for problems discovered during the ongoing string work in the main branch.
This release supports Python versions 3.12-3.15
Changes
=======
* Casting a fixed-width byte string array (``np.bytes_``) to ``StringDType`` now raises ``TypeError`` when the bytes are not valid UTF-8. Previously the invalid bytes were stored as-is and later caused undefined behavior in string operations.
(gh-32296 <https://github.com/numpy/numpy/pull/32296>__)
* ``MaskedArray._fill_value`` would become stale when ufuncs that change dtype left the result holding a fill_value typed for the old dtype. The mismatch was silent until something later called ``_check_fill_value``, such as ``.view()``, and then a ``TypeError`` would be raised. Now, when the copied fill_value is no longer valid for the new dtype, fall back to the default fill_value for that dtype instead of propagating the stale value. This may raise a ``ComplexWarning`` if the fill_value is complex and the new dtype is real.
(gh-32423 <https://github.com/numpy/numpy/pull/32423>__)
---
.../python/{python3-numpy_2.5.2.bb => python3-numpy_2.5.3.bb} | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
rename meta/recipes-devtools/python/{python3-numpy_2.5.2.bb => python3-numpy_2.5.3.bb} (97%)meta/recipes-devtools/python/python3-numpy_2.5.3.bb renamed from meta/recipes-devtools/python/python3-numpy_2.5.2.bb +1 -1
@@ -10,7 +10,7 @@ SRCNAME = "numpy" SRC_URI = "${GITHUB_BASE_URI}/download/v${PV}/${SRCNAME}-${PV}.tar.gz \ file://run-ptest \ " -SRC_URI[sha256sum] = "d482d171c406ae88c5b19cad3b6a1c4c5209f886ab74bc44c2c865c23f52d860" +SRC_URI[sha256sum] = "df2d5874ff183595a4ba404edd04f6bd9b5505c1d7708573f6a6c17489a67563" GITHUB_BASE_URI = "https://github.com/numpy/numpy/releases" UPSTREAM_CHECK_REGEX = "releases/tag/v?(?P<pver>\d+(\.\d+)+)$"