From: "Leon Anavi" <leon.anavi@konsulko.com>
To: openembedded-devel@lists.openembedded.org
Cc: Leon Anavi <leon.anavi@konsulko.com>
Subject: [meta-python][PATCH 2/2] python3-cffi: Upgrade 1.14.3 -> 1.14.4
Date: Tue, 12 Jan 2021 19:56:41 +0200 [thread overview]
Message-ID: <20210112175641.5003-2-leon.anavi@konsulko.com> (raw)
In-Reply-To: <20210112175641.5003-1-leon.anavi@konsulko.com>
Upgrade to release 1.14.4:
- Release done for pip reasons.
Signed-off-by: Leon Anavi <leon.anavi@konsulko.com>
---
.../python/{python3-cffi_1.14.3.bb => python3-cffi_1.14.4.bb} | 3 +--
1 file changed, 1 insertion(+), 2 deletions(-)
rename meta-python/recipes-devtools/python/{python3-cffi_1.14.3.bb => python3-cffi_1.14.4.bb} (75%)
diff --git a/meta-python/recipes-devtools/python/python3-cffi_1.14.3.bb b/meta-python/recipes-devtools/python/python3-cffi_1.14.4.bb
similarity index 75%
rename from meta-python/recipes-devtools/python/python3-cffi_1.14.3.bb
rename to meta-python/recipes-devtools/python/python3-cffi_1.14.4.bb
index dbdd16f66..45962c6ce 100644
--- a/meta-python/recipes-devtools/python/python3-cffi_1.14.3.bb
+++ b/meta-python/recipes-devtools/python/python3-cffi_1.14.4.bb
@@ -4,8 +4,7 @@ LICENSE = "MIT"
LIC_FILES_CHKSUM = "file://LICENSE;md5=5677e2fdbf7cdda61d6dd2b57df547bf"
DEPENDS += "libffi ${PYTHON_PN}-pycparser"
-SRC_URI[md5sum] = "c2a47ffd5d183b193ac8ed3414dcfd07"
-SRC_URI[sha256sum] = "f92f789e4f9241cd262ad7a555ca2c648a98178a953af117ef7fad46aa1d5591"
+SRC_URI[sha256sum] = "1a465cbe98a7fd391d47dce4b8f7e5b921e6cd805ef421d04f5f66ba8f06086c"
inherit pypi setuptools3
--
2.17.1
next prev parent reply other threads:[~2021-01-12 17:56 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-01-12 17:56 [meta-python][PATCH 1/2] python3-pyscaffold: Upgrade 3.2.3 -> 3.3 Leon Anavi
2021-01-12 17:56 ` Leon Anavi [this message]
2021-01-14 18:43 ` [oe] [meta-python][PATCH 2/2] python3-cffi: Upgrade 1.14.3 -> 1.14.4 Trevor Gamblin
2021-01-14 18:42 ` [oe] [meta-python][PATCH 1/2] python3-pyscaffold: Upgrade 3.2.3 -> 3.3 Trevor Gamblin
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=20210112175641.5003-2-leon.anavi@konsulko.com \
--to=leon.anavi@konsulko.com \
--cc=openembedded-devel@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.