From: Jaipaul Cheernam <jaipaul.cheernam@est.tech>
To: openembedded-core@lists.openembedded.org
Subject: [PATCH v2] python3-pycryptodome: upgrade 3.24.1 -> 4.2.0
Date: Mon, 26 Oct 2026 11:57:45 +0100 [thread overview]
Message-ID: <20261026105745.3438-1-jaipaul.cheernam@est.tech> (raw)
In-Reply-To: <20261026103138.3137-11-jaipaul.cheernam@est.tech>
ChangeLog: https://www.pycryptodome.org/src/changelog#october-2026
https://github.com/Legrandin/pycryptodome/blob/v4.2.0/Changelog.rst#420-24-october-2026
License-Update: Update to license text [1], [2] and [3]
[1] https://github.com/Legrandin/pycryptodome/commit/65aa57f08db0afb1a3d3887164a0027654b55931
[2] https://github.com/Legrandin/pycryptodome/commit/43b28d7170ccebfc51c9148e723aa881fb32a1dc
[3] https://github.com/Legrandin/pycryptodome/commit/04a1ad1d286eb843ac62abfc05ed58df99eaf27b
Signed-off-by: Jaipaul Cheernam <jaipaul.cheernam@est.tech>
---
Changes Since v1:
- Fix patch Author from AUH
meta/recipes-devtools/python/python-pycryptodome.inc | 2 +-
...on3-pycryptodome_3.24.1.bb => python3-pycryptodome_4.2.0.bb} | 2 +-
2 files changed, 2 insertions(+), 2 deletions(-)
rename meta/recipes-devtools/python/{python3-pycryptodome_3.24.1.bb => python3-pycryptodome_4.2.0.bb} (56%)
diff --git a/meta/recipes-devtools/python/python-pycryptodome.inc b/meta/recipes-devtools/python/python-pycryptodome.inc
index a0181874cd2..8f2b9025ddb 100644
--- a/meta/recipes-devtools/python/python-pycryptodome.inc
+++ b/meta/recipes-devtools/python/python-pycryptodome.inc
@@ -3,7 +3,7 @@ DESCRIPTION = "PyCryptodome is a self-contained Python package of low-level\
cryptographic primitives."
HOMEPAGE = "http://www.pycryptodome.org"
LICENSE = "BSD-2-Clause AND Unlicense"
-LIC_FILES_CHKSUM = "file://LICENSE.rst;md5=29242a70410a4eeff488a28164e7ab93"
+LIC_FILES_CHKSUM = "file://LICENSE.rst;md5=a514b4a7ad24677ae50f3becb03404e3"
inherit pypi
diff --git a/meta/recipes-devtools/python/python3-pycryptodome_3.24.1.bb b/meta/recipes-devtools/python/python3-pycryptodome_4.2.0.bb
similarity index 56%
rename from meta/recipes-devtools/python/python3-pycryptodome_3.24.1.bb
rename to meta/recipes-devtools/python/python3-pycryptodome_4.2.0.bb
index 0aa53559d67..13c572b7c89 100644
--- a/meta/recipes-devtools/python/python3-pycryptodome_3.24.1.bb
+++ b/meta/recipes-devtools/python/python3-pycryptodome_4.2.0.bb
@@ -1,6 +1,6 @@
require python-pycryptodome.inc
inherit python_setuptools_build_meta
-SRC_URI[sha256sum] = "3f9e74444c0ecbec7af232a95d282c74b114d53212ce075ed17b7fd7dca32bb3"
+SRC_URI[sha256sum] = "21d7fdba239d6ef863d3d08388801c683453a3bb4897c2b27f27847aad89bdf7"
CVE_PRODUCT = "pycryptodome:pycryptodome"
next prev parent reply other threads:[~2026-10-26 10:57 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-10-26 10:31 [PATCH 01/12] libsoup: upgrade 3.8.0 -> 3.8.1 Jaipaul Cheernam
2026-10-26 10:31 ` [PATCH 02/12] libsolv: upgrade 0.7.40 -> 0.7.41 Jaipaul Cheernam
2026-10-26 10:31 ` [PATCH 03/12] patch: upgrade 2.8 -> 2.8.1 Jaipaul Cheernam
2026-10-26 10:31 ` [PATCH 04/12] python3-certifi: upgrade 2026.10.19 -> 2026.10.23 Jaipaul Cheernam
2026-10-26 10:31 ` [PATCH 05/12] python3-cython: upgrade 3.2.9 -> 3.3.0 Jaipaul Cheernam
2026-10-27 8:11 ` [OE-core] " Mathieu Dubois-Briand
2026-10-27 11:19 ` Jaipaul Cheernam
2026-10-26 10:31 ` [PATCH 06/12] python3-hypothesis: upgrade 6.169.0 -> 6.170.9 Jaipaul Cheernam
2026-10-26 10:31 ` [PATCH 07/12] valgrind: upgrade 3.27.1 -> 3.28.0 Jaipaul Cheernam
2026-10-26 10:31 ` [PATCH 08/12] librsvg: upgrade 2.63.3 -> 2.63.4 Jaipaul Cheernam
2026-10-26 10:31 ` [PATCH 09/12] libslirp: upgrade 4.9.5 -> 4.9.6 Jaipaul Cheernam
2026-10-26 10:31 ` [PATCH 10/12] python3-jsonpointer: upgrade 3.4 -> 3.5 Jaipaul Cheernam
2026-10-26 10:31 ` [PATCH 11/12] python3-pycryptodome: upgrade 3.24.1 -> 4.2.0 Jaipaul Cheernam
2026-10-26 10:51 ` Patchtest results for " patchtest
2026-10-26 10:57 ` Jaipaul Cheernam [this message]
2026-10-27 8:16 ` [OE-core] " Mathieu Dubois-Briand
2026-10-27 8:45 ` Jaipaul Cheernam
2026-10-26 10:31 ` [PATCH 12/12] python3-wcwidth: upgrade 0.9.1 -> 0.9.4 Jaipaul Cheernam
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=20261026105745.3438-1-jaipaul.cheernam@est.tech \
--to=jaipaul.cheernam@est.tech \
--cc=openembedded-core@lists.openembedded.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