From: <wangmy@fujitsu.com>
To: <openembedded-core@lists.openembedded.org>
Cc: Wang Mingyu <wangmy@fujitsu.com>
Subject: [OE-core] [PATCH] python3-importlib-metadata: upgrade 6.0.0 -> 6.2.0
Date: Mon, 10 Apr 2023 17:37:19 +0800 [thread overview]
Message-ID: <1681119440-25219-4-git-send-email-wangmy@fujitsu.com> (raw)
In-Reply-To: <1681119440-25219-1-git-send-email-wangmy@fujitsu.com>
From: Wang Mingyu <wangmy@fujitsu.com>
Changelog:
===========
- #384: PackageMetadata now stipulates an additional get method allowing for
easy querying of metadata keys that may not be present.
- #428: packages_distributions now honors packages and modules with Python
modules that not .py sources (e.g. .pyc, .so).
- #434: Expand protocol for PackageMetadata.get_all to match the upstream
implementation of email.message.Message.get_all in python/typeshed#9620.
Signed-off-by: Wang Mingyu <wangmy@fujitsu.com>
---
...ib-metadata_6.0.0.bb => python3-importlib-metadata_6.2.0.bb} | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
rename meta/recipes-devtools/python/{python3-importlib-metadata_6.0.0.bb => python3-importlib-metadata_6.2.0.bb} (88%)
diff --git a/meta/recipes-devtools/python/python3-importlib-metadata_6.0.0.bb b/meta/recipes-devtools/python/python3-importlib-metadata_6.2.0.bb
similarity index 88%
rename from meta/recipes-devtools/python/python3-importlib-metadata_6.0.0.bb
rename to meta/recipes-devtools/python/python3-importlib-metadata_6.2.0.bb
index b33a1b5858..b7bc91552e 100644
--- a/meta/recipes-devtools/python/python3-importlib-metadata_6.0.0.bb
+++ b/meta/recipes-devtools/python/python3-importlib-metadata_6.2.0.bb
@@ -8,7 +8,7 @@ inherit pypi python_setuptools_build_meta
PYPI_PACKAGE = "importlib_metadata"
UPSTREAM_CHECK_REGEX = "/importlib-metadata/(?P<pver>(\d+[\.\-_]*)+)/"
-SRC_URI[sha256sum] = "e354bedeb60efa6affdcc8ae121b73544a7aa74156d047311948f6d711cd378d"
+SRC_URI[sha256sum] = "9127aad2f49d7203e7112098c12b92e4fd1061ccd18548cdfdc49171a8c073cc"
S = "${WORKDIR}/importlib_metadata-${PV}"
--
2.34.1
next prev parent reply other threads:[~2023-04-10 9:37 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-04-10 9:37 [OE-core] [PATCH] python3-cryptography-vectors: upgrade 39.0.2 -> 40.0.1 wangmy
2023-04-10 9:37 ` [OE-core] [PATCH] python3-cython: upgrade 0.29.33 -> 0.29.34 wangmy
2023-04-10 9:37 ` [OE-core] [PATCH] python3-hypothesis: upgrade 6.68.2 -> 6.71.0 wangmy
2023-04-10 9:37 ` wangmy [this message]
2023-04-10 9:37 ` [OE-core] [PATCH] zstd: upgrade 1.5.4 -> 1.5.5 wangmy
2023-04-12 7:35 ` Luca Ceresoli
2023-04-10 16:17 ` [OE-core] [PATCH] python3-cryptography-vectors: upgrade 39.0.2 -> 40.0.1 Tim Orling
2023-04-10 17:25 ` Alexandre Belloni
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=1681119440-25219-4-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