From: Wang Mingyu <wangmy@cn.fujitsu.com>
To: <openembedded-devel@lists.openembedded.org>
Subject: [meta-python][PATCH] python-pbr: upgrade 5.4.3 -> 5.4.4
Date: Mon, 2 Dec 2019 07:28:14 -0800 [thread overview]
Message-ID: <1575300494-101612-5-git-send-email-wangmy@cn.fujitsu.com> (raw)
In-Reply-To: <1575300494-101612-1-git-send-email-wangmy@cn.fujitsu.com>
Signed-off-by: Wang Mingyu <wangmy@cn.fujitsu.com>
---
.../python/{python-pbr_5.4.3.bb => python-pbr_5.4.4.bb} | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
rename meta-python/recipes-devtools/python/{python-pbr_5.4.3.bb => python-pbr_5.4.4.bb} (62%)
diff --git a/meta-python/recipes-devtools/python/python-pbr_5.4.3.bb b/meta-python/recipes-devtools/python/python-pbr_5.4.4.bb
similarity index 62%
rename from meta-python/recipes-devtools/python/python-pbr_5.4.3.bb
rename to meta-python/recipes-devtools/python/python-pbr_5.4.4.bb
index b21722f..9d7d8d7 100644
--- a/meta-python/recipes-devtools/python/python-pbr_5.4.3.bb
+++ b/meta-python/recipes-devtools/python/python-pbr_5.4.4.bb
@@ -2,8 +2,8 @@ inherit setuptools
# The inc file is in oe-core
require recipes-devtools/python/python-pbr.inc
-SRC_URI[md5sum] = "477d2aa285ad97250a172b199f4060b7"
-SRC_URI[sha256sum] = "2c8e420cd4ed4cec4e7999ee47409e876af575d4c35a45840d59e8b5f3155ab8"
+SRC_URI[md5sum] = "65cdc32e1a1ff56d481fc15aa8caf988"
+SRC_URI[sha256sum] = "139d2625547dbfa5fb0b81daebb39601c478c21956dc57e2e07b74450a8c506b"
do_install_append() {
if [ -f ${D}${bindir}/pbr ]; then
--
2.7.4
prev parent reply other threads:[~2019-12-02 9:00 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-12-02 15:28 [meta-python][PATCH] python-pytest: upgrade 5.2.2 -> 5.3.1 Wang Mingyu
2019-12-02 15:28 ` [meta-python][PATCH] python-thrift: upgrade 0.11.0 -> 0.13.0 Wang Mingyu
2019-12-02 15:28 ` [meta-python][PATCH] python-alembic: upgrade 1.3.0 -> 1.3.1 Wang Mingyu
2019-12-02 15:28 ` [meta-python][PATCH] python-dbus: upgrade 1.2.12 -> 1.2.14 Wang Mingyu
2019-12-02 15:28 ` 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=1575300494-101612-5-git-send-email-wangmy@cn.fujitsu.com \
--to=wangmy@cn.fujitsu.com \
--cc=openembedded-devel@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.