From: <wangmy@fujitsu.com>
To: <openembedded-core@lists.openembedded.org>
Cc: Wang Mingyu <wangmy@fujitsu.com>
Subject: [oe] [meta-python] [PATCH] python3-web3: upgrade 6.1.0 -> 6.2.0
Date: Mon, 17 Apr 2023 14:52:19 +0800 [thread overview]
Message-ID: <1681714339-18687-5-git-send-email-wangmy@fujitsu.com> (raw)
In-Reply-To: <1681714339-18687-1-git-send-email-wangmy@fujitsu.com>
From: Wang Mingyu <wangmy@fujitsu.com>
Signed-off-by: Wang Mingyu <wangmy@fujitsu.com>
---
.../python/{python3-web3_6.1.0.bb => python3-web3_6.2.0.bb} | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
rename meta-python/recipes-devtools/python/{python3-web3_6.1.0.bb => python3-web3_6.2.0.bb} (84%)
diff --git a/meta-python/recipes-devtools/python/python3-web3_6.1.0.bb b/meta-python/recipes-devtools/python/python3-web3_6.2.0.bb
similarity index 84%
rename from meta-python/recipes-devtools/python/python3-web3_6.1.0.bb
rename to meta-python/recipes-devtools/python/python3-web3_6.2.0.bb
index b813e632b..8e09cabbb 100644
--- a/meta-python/recipes-devtools/python/python3-web3_6.1.0.bb
+++ b/meta-python/recipes-devtools/python/python3-web3_6.2.0.bb
@@ -4,7 +4,7 @@ SECTION = "devel/python"
LICENSE = "MIT"
LIC_FILES_CHKSUM = "file://LICENSE;md5=1dc2732bdc5e50382737979791cbb3b7"
-SRC_URI[sha256sum] = "55e58f2b8705f0911db5a395343b158d5e4edae9973f5dcb349512ae5a349af5"
+SRC_URI[sha256sum] = "7695ee81162c644de0dfd0f5372f96a73be557b46365d218f581ca10197c6389"
inherit pypi setuptools3
--
2.34.1
prev parent reply other threads:[~2023-04-17 6:53 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-04-17 6:52 [oe] [meta-python] [PATCH] python3-google-auth: upgrade 2.17.2 -> 2.17.3 wangmy
2023-04-17 6:52 ` [oe] [meta-python] [PATCH] python3-protobuf: upgrade 4.22.1 -> 4.22.3 wangmy
2023-04-17 6:52 ` [oe] [meta-python] [PATCH] python3-pymisp: upgrade 2.4.169.3 -> 2.4.170 wangmy
2023-04-17 6:52 ` [oe] [meta-python] [PATCH] python3-rich: upgrade 13.3.3 -> 13.3.4 wangmy
2023-04-17 6:52 ` wangmy [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=1681714339-18687-5-git-send-email-wangmy@fujitsu.com \
--to=wangmy@fujitsu.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