From: Wang Mingyu <wangmy@fujitsu.com>
To: <openembedded-core@lists.openembedded.org>
Cc: Wang Mingyu <wangmy@fujitsu.com>
Subject: [OE-core] [PATCH] python3-mako: upgrade 1.2.1 -> 1.2.2
Date: Mon, 5 Sep 2022 17:06:19 +0800 [thread overview]
Message-ID: <1662368782-32326-1-git-send-email-wangmy@fujitsu.com> (raw)
Signed-off-by: Wang Mingyu <wangmy@fujitsu.com>
---
.../python/{python3-mako_1.2.1.bb => python3-mako_1.2.2.bb} | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
rename meta/recipes-devtools/python/{python3-mako_1.2.1.bb => python3-mako_1.2.2.bb} (85%)
diff --git a/meta/recipes-devtools/python/python3-mako_1.2.1.bb b/meta/recipes-devtools/python/python3-mako_1.2.2.bb
similarity index 85%
rename from meta/recipes-devtools/python/python3-mako_1.2.1.bb
rename to meta/recipes-devtools/python/python3-mako_1.2.2.bb
index 8155c37984..e3774ee621 100644
--- a/meta/recipes-devtools/python/python3-mako_1.2.1.bb
+++ b/meta/recipes-devtools/python/python3-mako_1.2.2.bb
@@ -8,7 +8,7 @@ PYPI_PACKAGE = "Mako"
inherit pypi python_setuptools_build_meta
-SRC_URI[sha256sum] = "f054a5ff4743492f1aa9ecc47172cb33b42b9d993cffcc146c9de17e717b0307"
+SRC_URI[sha256sum] = "3724869b363ba630a272a5f89f68c070352137b8fd1757650017b7e06fda163f"
RDEPENDS:${PN} = "${PYTHON_PN}-html \
${PYTHON_PN}-markupsafe \
--
2.25.1
next reply other threads:[~2022-09-05 9:06 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-09-05 9:06 Wang Mingyu [this message]
2022-09-05 9:06 ` [OE-core] [PATCH] python3-pathspec: upgrade 0.9.0 -> 0.10.1 Wang Mingyu
2022-09-05 9:06 ` [OE-core] [PATCH] python3-pytest: upgrade 7.1.2 -> 7.1.3 Wang Mingyu
2022-09-05 9:06 ` [OE-core] [PATCH] vala: upgrade 0.56.2 -> 0.56.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=1662368782-32326-1-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