From: tim.orling@konsulko.com
To: openembedded-core@lists.openembedded.org
Cc: Tim Orling <tim.orling@konsulko.com>
Subject: [PATCH] python3-cffi: upgrade 2.1.0 -> 2.1.1
Date: Tue, 4 Aug 2026 08:06:00 -0700 [thread overview]
Message-ID: <20260804150559.2506646-2-tim.orling@konsulko.com> (raw)
From: Tim Orling <tim.orling@konsulko.com>
For a full comparison of changes (2 commits, 9 files changed), see:
https://github.com/python-cffi/cffi/compare/v2.1.0...v2.1.1
Upstream release notes:
https://cffi.readthedocs.io/en/stable/whatsnew.html#v2-1-1
v2.1.1
======
* Minimize internal Python API usage for interpreter and thread state
sampling where possible. Avoids breaking ABI change in
Python >= 3.15.0b4. (#269)
Signed-off-by: Tim Orling <tim.orling@konsulko.com>
---
No surprises in ptests on qemux86-64 (core-image-ptest-python3-cffi
target):
Testsuite summary
TOTAL: 1840
PASS: 1734
SKIP: 102
XFAIL: 4
FAIL: 0
XPASS: 0
ERROR: 0
DURATION: 189
.../python/{python3-cffi_2.1.0.bb => python3-cffi_2.1.1.bb} | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
rename meta/recipes-devtools/python/{python3-cffi_2.1.0.bb => python3-cffi_2.1.1.bb} (91%)
diff --git a/meta/recipes-devtools/python/python3-cffi_2.1.0.bb b/meta/recipes-devtools/python/python3-cffi_2.1.1.bb
similarity index 91%
rename from meta/recipes-devtools/python/python3-cffi_2.1.0.bb
rename to meta/recipes-devtools/python/python3-cffi_2.1.1.bb
index 718e43e339..455732a269 100644
--- a/meta/recipes-devtools/python/python3-cffi_2.1.0.bb
+++ b/meta/recipes-devtools/python/python3-cffi_2.1.1.bb
@@ -4,7 +4,7 @@ LICENSE = "MIT-0"
LIC_FILES_CHKSUM = "file://LICENSE;md5=c0158ab9b75875f3bb7fea081d388818"
DEPENDS += "libffi python3-pycparser"
-SRC_URI[sha256sum] = "efc1cdd798b1aaf39b4610bba7aad28c9bea9b910f25c784ccf9ec1fa719d1f9"
+SRC_URI[sha256sum] = "dd31f52ea1086513bb9df30f8fcee9b8918323ae067a3d5b78bc826a000712be"
SRC_URI += "file://run-ptest"
--
2.47.3
reply other threads:[~2026-08-04 15:07 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20260804150559.2506646-2-tim.orling@konsulko.com \
--to=tim.orling@konsulko.com \
--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;
as well as URLs for NNTP newsgroup(s).