From: Wang Mingyu <wangmy@fujitsu.com>
To: <openembedded-core@lists.openembedded.org>
Cc: Wang Mingyu <wangmy@fujitsu.com>
Subject: [OE-core] [PATCH] python3-hatchling: upgrade 1.5.0 -> 1.6.0
Date: Wed, 3 Aug 2022 16:40:30 +0800 [thread overview]
Message-ID: <1659516030-31123-4-git-send-email-wangmy@fujitsu.com> (raw)
In-Reply-To: <1659516030-31123-1-git-send-email-wangmy@fujitsu.com>
Signed-off-by: Wang Mingyu <wangmy@fujitsu.com>
---
.../{python3-hatchling_1.5.0.bb => python3-hatchling_1.6.0.bb} | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
rename meta/recipes-devtools/python/{python3-hatchling_1.5.0.bb => python3-hatchling_1.6.0.bb} (85%)
diff --git a/meta/recipes-devtools/python/python3-hatchling_1.5.0.bb b/meta/recipes-devtools/python/python3-hatchling_1.6.0.bb
similarity index 85%
rename from meta/recipes-devtools/python/python3-hatchling_1.5.0.bb
rename to meta/recipes-devtools/python/python3-hatchling_1.6.0.bb
index 61b3e87b92..e06bdf02ec 100644
--- a/meta/recipes-devtools/python/python3-hatchling_1.5.0.bb
+++ b/meta/recipes-devtools/python/python3-hatchling_1.6.0.bb
@@ -8,7 +8,7 @@ inherit pypi python_hatchling
DEPENDS += "python3-pluggy-native python3-tomli-native python3-pathspec-native python3-packaging-native python3-editables-native"
DEPENDS:remove:class-native = "python3-hatchling-native"
-SRC_URI[sha256sum] = "9ca409a41140cc662164680b78adcd3ba77b23a945984bd9970d11fe38e86a38"
+SRC_URI[sha256sum] = "bd6e8505de511ac4217ff50927f6d1845494608e401e63a62b830c31fb613544"
do_compile:prepend() {
export PYTHONPATH=src
--
2.25.1
prev parent reply other threads:[~2022-08-03 8:41 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-08-03 8:40 [OE-core] [PATCH] python3-attrs: upgrade 21.4.0 -> 22.1.0 Wang Mingyu
2022-08-03 8:40 ` [OE-core] [PATCH] python3-cython: upgrade 0.29.30 -> 0.29.32 Wang Mingyu
2022-08-03 8:40 ` [OE-core] [PATCH] python3-dbusmock: upgrade 0.28.1 -> 0.28.4 Wang Mingyu
2022-08-03 8:40 ` Wang Mingyu [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=1659516030-31123-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