From: Wang Mingyu <wangmy@fujitsu.com>
To: <openembedded-core@lists.openembedded.org>
Cc: Wang Mingyu <wangmy@fujitsu.com>
Subject: [OE-core] [PATCH] python3-dtschema: upgrade 2022.8.1 -> 2022.8.3
Date: Mon, 5 Sep 2022 17:03:21 +0800 [thread overview]
Message-ID: <1662368601-32265-5-git-send-email-wangmy@fujitsu.com> (raw)
In-Reply-To: <1662368601-32265-1-git-send-email-wangmy@fujitsu.com>
Signed-off-by: Wang Mingyu <wangmy@fujitsu.com>
---
...ython3-dtschema_2022.8.1.bb => python3-dtschema_2022.8.3.bb} | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
rename meta/recipes-devtools/python/{python3-dtschema_2022.8.1.bb => python3-dtschema_2022.8.3.bb} (83%)
diff --git a/meta/recipes-devtools/python/python3-dtschema_2022.8.1.bb b/meta/recipes-devtools/python/python3-dtschema_2022.8.3.bb
similarity index 83%
rename from meta/recipes-devtools/python/python3-dtschema_2022.8.1.bb
rename to meta/recipes-devtools/python/python3-dtschema_2022.8.3.bb
index 38f646e50a..bc819c0dd6 100644
--- a/meta/recipes-devtools/python/python3-dtschema_2022.8.1.bb
+++ b/meta/recipes-devtools/python/python3-dtschema_2022.8.3.bb
@@ -7,7 +7,7 @@ inherit pypi setuptools3
PYPI_PACKAGE = "dtschema"
-SRC_URI[sha256sum] = "3e56a9920944223d6f93fd51ada19dd8db554ac9182ef52c1c5c9d4966ab30aa"
+SRC_URI[sha256sum] = "128c88a393cd04154cef4d4b10a643e4473ae290b436e8e61d2e97ae8e53255d"
DEPENDS += "python3-setuptools-scm-native"
RDEPENDS:${PN} += "python3-ruamel-yaml python3-jsonschema python3-rfc3987"
--
2.25.1
prev parent reply other threads:[~2022-09-05 9:04 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-09-05 9:03 [OE-core] [PATCH] cracklib: upgrade 2.9.7 -> 2.9.8 Wang Mingyu
2022-09-05 9:03 ` [OE-core] [PATCH] kmscube: upgrade to latest revision Wang Mingyu
2022-09-05 9:03 ` [OE-core] [PATCH] mesa: upgrade 22.1.6 -> 22.1.7 Wang Mingyu
2022-09-05 9:03 ` [OE-core] [PATCH] piglit: upgrade to latest revision Wang Mingyu
2022-09-05 9:03 ` 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=1662368601-32265-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