From: Richard Purdie <richard.purdie@linuxfoundation.org>
To: openembedded-core@lists.openembedded.org
Subject: [PATCH 5/5] python3-pyopenssl: upgrade 26.3.0 -> 26.4.0
Date: Sun, 2 Aug 2026 13:56:07 +0100 [thread overview]
Message-ID: <20260802125609.4049666-5-richard.purdie@linuxfoundation.org> (raw)
In-Reply-To: <20260802125609.4049666-1-richard.purdie@linuxfoundation.org>
26.4.0 (2026-08-01)
-------------------
Changes:
^^^^^^^^
- Maximum supported ``cryptography`` version is now 50.x.
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
---
...{python3-pyopenssl_26.3.0.bb => python3-pyopenssl_26.4.0.bb} | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
rename meta/recipes-devtools/python/{python3-pyopenssl_26.3.0.bb => python3-pyopenssl_26.4.0.bb} (87%)
diff --git a/meta/recipes-devtools/python/python3-pyopenssl_26.3.0.bb b/meta/recipes-devtools/python/python3-pyopenssl_26.4.0.bb
similarity index 87%
rename from meta/recipes-devtools/python/python3-pyopenssl_26.3.0.bb
rename to meta/recipes-devtools/python/python3-pyopenssl_26.4.0.bb
index ca6754d4620..6246375afc5 100644
--- a/meta/recipes-devtools/python/python3-pyopenssl_26.3.0.bb
+++ b/meta/recipes-devtools/python/python3-pyopenssl_26.4.0.bb
@@ -5,7 +5,7 @@ LIC_FILES_CHKSUM = "file://LICENSE;md5=3b83ef96387f14655fc854ddc3c6bd57"
DEPENDS += "openssl python3-cryptography"
-SRC_URI[sha256sum] = "589de7fae1c9ea670d18422ed00fc04da787bbde8e1454aea872aa57b49ad341"
+SRC_URI[sha256sum] = "28dfcce0162b9211413e26dfbfdf1d24317fbeba18fc93c12400a1856b2a0bc7"
inherit pypi setuptools3
prev parent reply other threads:[~2026-08-02 12:56 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-08-02 12:56 [PATCH 1/5] at-spi2-core: upgrade 2.60.5 -> 2.60.6 Richard Purdie
2026-08-02 12:56 ` [PATCH 2/5] libmicrohttpd: upgrade 1.0.8 -> 1.0.9 Richard Purdie
2026-08-02 12:56 ` [PATCH 3/5] libpsl: upgrade 0.23.0 -> 0.23.1 Richard Purdie
2026-08-02 12:56 ` [PATCH 4/5] pkgconf: upgrade 3.0.4 -> 3.0.5 Richard Purdie
2026-08-02 12:56 ` Richard Purdie [this message]
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=20260802125609.4049666-5-richard.purdie@linuxfoundation.org \
--to=richard.purdie@linuxfoundation.org \
--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