deleted file mode 100644
@@ -1,6 +0,0 @@
-require python-pycryptodome.inc
-inherit python_setuptools_build_meta
-
-SRC_URI[sha256sum] = "3f9e74444c0ecbec7af232a95d282c74b114d53212ce075ed17b7fd7dca32bb3"
-
-CVE_PRODUCT = "pycryptodome:pycryptodome"
new file mode 100644
@@ -0,0 +1,47 @@
+# FIXME: the LIC_FILES_CHKSUM values have been updated by 'devtool upgrade'.
+# The following is the difference between the old and the new license text.
+# Please update the LICENSE value if needed, and summarize the changes in
+# the commit message via 'License-Update:' tag.
+# (example: 'License-Update: copyright years updated.')
+#
+# The changes:
+#
+# --- LICENSE.rst
+# +++ LICENSE.rst
+# @@ -3,6 +3,10 @@
+#
+# In either case, there are minimal if no restrictions on the redistribution,
+# modification and usage of the software.
+# +
+# +Files that do not include the license text refer to it with an SPDX tag:
+# +``SPDX-License-Identifier: BSD-2-Clause`` for the BSD license below
+# +(``SPDX-FileCopyrightText`` gives the copyright notice).
+#
+# Public domain
+# =============
+# @@ -59,3 +63,16 @@
+# CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY,
+# OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE
+# OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.
+# +
+# +Third-party code
+# +================
+# +
+# +The directory ``src/mldsa-native`` contains code from mldsa-native
+# +(https://github.com/pq-code-package/mldsa-native), available under
+# +the Apache-2.0 license OR the ISC license OR the MIT license.
+# +See ``src/mldsa-native/LICENSE`` for the full text of the licenses.
+# +
+# +The directory ``src/mlkem-native`` contains code from mlkem-native
+# +(https://github.com/pq-code-package/mlkem-native), available under
+# +the Apache-2.0 license OR the ISC license OR the MIT license.
+# +See ``src/mlkem-native/LICENSE`` for the full text of the licenses.
+#
+#
+
+require python-pycryptodome.inc
+inherit python_setuptools_build_meta
+
+SRC_URI[sha256sum] = "eab7620c60c85f3fa251d026ec06e094f036d96187bebb9752e46fbcebabbb55"
+
+CVE_PRODUCT = "pycryptodome:pycryptodome"
similarity index 76%
rename from meta/recipes-devtools/python/python3-pycryptodomex_3.24.1.bb
rename to meta/recipes-devtools/python/python3-pycryptodomex_3.24.2.bb
@@ -1,7 +1,7 @@
require python-pycryptodome.inc
inherit python_setuptools_build_meta
-SRC_URI[sha256sum] = "09081666ffc599976c0b8b29caf2cf82212c0f05bed233c8f8ed53e4f6e1d356"
+SRC_URI[sha256sum] = "e4dbc29e2575365d15e272f769329106277649aea081e2119cf43d66950f8f8f"
CVE_PRODUCT = "pycryptodome:pycryptodome pycryptodome:pycryptodomex"
Hello, this email is a notification from the Auto Upgrade Helper that the automatic attempt to upgrade the recipe(s) *python3-pycryptodome,python3-pycryptodomex* to *4.4.0,3.24.2* has Failed(do_compile). Detailed error information: do_compile failed Next steps: - apply the patch: git am 0001-python3-pycryptodome-python3-pycryptodomex-upgrade-3.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 fa99ba835da15fe5e349a7a1de6aee4debe9ee00 Mon Sep 17 00:00:00 2001 From: Upgrade Helper <auh@yoctoproject.org> Date: Sun, 8 Nov 2026 05:08:06 +0000 Subject: [PATCH] python3-pycryptodome,python3-pycryptodomex: upgrade 3.24.1 -> 4.4.0,3.24.1 -> 3.24.2 4.4.0 (7 November 2026) New features ------------ Resolved issues --------------- 4.3.0 (2 November 2026) New features ------------ Other changes ------------- Resolved issues --------------- 4.2.0 (24 October 2026) New features ------------ 4.1.0 (19 October 2026) New features ------------ Resolved issues --------------- 4.0.1 (17 October 2026) New features ------------ 4.0.0 (14 October 2026) Breaking changes ---------------- Deprecations ------------ Resolved issues --------------- New features ------------ 3.24.2 (5 November 2026) This release is only for ``pycryptodomex``. Resolved issues --------------- Other changes ------------- 3.24.2 (5 November 2026) This release is only for ``pycryptodomex``. Resolved issues --------------- Other changes ------------- --- .../python/python3-pycryptodome_3.24.1.bb | 6 --- .../python/python3-pycryptodome_4.4.0.bb | 47 +++++++++++++++++++ ...4.1.bb => python3-pycryptodomex_3.24.2.bb} | 2 +- 3 files changed, 48 insertions(+), 7 deletions(-) delete mode 100644 meta/recipes-devtools/python/python3-pycryptodome_3.24.1.bb create mode 100644 meta/recipes-devtools/python/python3-pycryptodome_4.4.0.bb rename meta/recipes-devtools/python/{python3-pycryptodomex_3.24.1.bb => python3-pycryptodomex_3.24.2.bb} (76%)