From: Wang Mingyu <wangmy@fujitsu.com>
To: <openembedded-devel@lists.openembedded.org>
Cc: Wang Mingyu <wangmy@fujitsu.com>
Subject: [oe] [meta-python] [PATCH] python3-absl: upgrade 0.15.0 -> 1.0.0
Date: Tue, 16 Nov 2021 11:35:53 +0800 [thread overview]
Message-ID: <1637033756-81253-1-git-send-email-wangmy@fujitsu.com> (raw)
Changed
absl-py no longer supports Python 2.7, 3.4, 3.5. All versions have reached
end-of-life for more than a year now.
New releases will be tagged as vX.Y.Z instead of pypi-vX.Y.Z in the git
repo going forward.
Signed-off-by: Wang Mingyu <wangmy@fujitsu.com>
---
.../python/{python3-absl_0.15.0.bb => python3-absl_1.0.0.bb} | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
rename meta-python/recipes-devtools/python/{python3-absl_0.15.0.bb => python3-absl_1.0.0.bb} (76%)
diff --git a/meta-python/recipes-devtools/python/python3-absl_0.15.0.bb b/meta-python/recipes-devtools/python/python3-absl_1.0.0.bb
similarity index 76%
rename from meta-python/recipes-devtools/python/python3-absl_0.15.0.bb
rename to meta-python/recipes-devtools/python/python3-absl_1.0.0.bb
index f25201dc3f..736e6a9444 100644
--- a/meta-python/recipes-devtools/python/python3-absl_0.15.0.bb
+++ b/meta-python/recipes-devtools/python/python3-absl_1.0.0.bb
@@ -4,7 +4,7 @@ SECTION = "devel/python"
LICENSE = "Apache-2.0"
LIC_FILES_CHKSUM = "file://LICENSE;md5=3b83ef96387f14655fc854ddc3c6bd57"
-SRC_URI[sha256sum] = "72d782fbeafba66ba3e525d46bccac949b9a174dbf66233e50ece09ee688dc81"
+SRC_URI[sha256sum] = "ac511215c01ee9ae47b19716599e8ccfa746f2e18de72bdf641b79b22afa27ea"
PYPI_PACKAGE = "absl-py"
--
2.25.1
next reply other threads:[~2021-11-16 3:36 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-11-16 3:35 Wang Mingyu [this message]
2021-11-16 3:35 ` [oe] [meta-python] [PATCH] python3-alembic: upgrade 1.7.4 -> 1.7.5 Wang Mingyu
2021-11-16 3:35 ` [oe] [meta-python] [PATCH] python3-cmd2: upgrade 2.2.0 -> 2.3.0 Wang Mingyu
2021-11-16 3:35 ` [oe] [meta-python] [PATCH] python3-gast: upgrade 0.5.2 -> 0.5.3 Wang Mingyu
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=1637033756-81253-1-git-send-email-wangmy@fujitsu.com \
--to=wangmy@fujitsu.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.