From: Wang Mingyu <wangmy@fujitsu.com>
To: <openembedded-core@lists.openembedded.org>
Cc: Wang Mingyu <wangmy@fujitsu.com>
Subject: [OE-core] [PATCH] python3-markupsafe: upgrade 2.1.0 -> 2.1.1
Date: Tue, 22 Mar 2022 18:39:46 +0800 [thread overview]
Message-ID: <1647945587-5282-2-git-send-email-wangmy@fujitsu.com> (raw)
In-Reply-To: <1647945587-5282-1-git-send-email-wangmy@fujitsu.com>
Signed-off-by: Wang Mingyu <wangmy@fujitsu.com>
---
...{python3-markupsafe_2.1.0.bb => python3-markupsafe_2.1.1.bb} | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
rename meta/recipes-devtools/python/{python3-markupsafe_2.1.0.bb => python3-markupsafe_2.1.1.bb} (87%)
diff --git a/meta/recipes-devtools/python/python3-markupsafe_2.1.0.bb b/meta/recipes-devtools/python/python3-markupsafe_2.1.1.bb
similarity index 87%
rename from meta/recipes-devtools/python/python3-markupsafe_2.1.0.bb
rename to meta/recipes-devtools/python/python3-markupsafe_2.1.1.bb
index 953ea01cfe..0544dd1b83 100644
--- a/meta/recipes-devtools/python/python3-markupsafe_2.1.0.bb
+++ b/meta/recipes-devtools/python/python3-markupsafe_2.1.1.bb
@@ -3,7 +3,7 @@ HOMEPAGE = "http://github.com/mitsuhiko/markupsafe"
LICENSE = "BSD-3-Clause"
LIC_FILES_CHKSUM = "file://LICENSE.rst;md5=ffeffa59c90c9c4a033c7574f8f3fb75"
-SRC_URI[sha256sum] = "80beaf63ddfbc64a0452b841d8036ca0611e049650e20afcb882f5d3c266d65f"
+SRC_URI[sha256sum] = "7f91197cc9e48f989d12e4e6fbc46495c446636dfc81b9ccf50bb0ec74b91d4b"
PYPI_PACKAGE = "MarkupSafe"
inherit pypi setuptools3
--
2.25.1
next prev parent reply other threads:[~2022-03-22 10:40 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-03-22 10:39 [OE-core] [PATCH] man-db: upgrade 2.10.1 -> 2.10.2 Wang Mingyu
2022-03-22 10:39 ` Wang Mingyu [this message]
2022-03-22 10:39 ` [OE-core] [PATCH] vala: upgrade 0.54.7 -> 0.56.0 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=1647945587-5282-2-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