From: Wang Mingyu <wangmy@fujitsu.com>
To: <openembedded-core@lists.openembedded.org>
Cc: Wang Mingyu <wangmy@fujitsu.com>
Subject: [OE-core] [PATCH] python3-dbusmock: upgrade 0.24.1 -> 0.25.0
Date: Mon, 27 Dec 2021 17:08:47 +0800 [thread overview]
Message-ID: <1640596128-22182-1-git-send-email-wangmy@fujitsu.com> (raw)
Changelog:
========
bluez template: Implement adapter discovery, connect, disconnect, and removal
Fix changing array properties
Fix CLI upower tests
Add testing and Fedora updating through packit
Signed-off-by: Wang Mingyu <wangmy@fujitsu.com>
---
.../{python3-dbusmock_0.24.1.bb => python3-dbusmock_0.25.0.bb} | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
rename meta/recipes-devtools/python/{python3-dbusmock_0.24.1.bb => python3-dbusmock_0.25.0.bb} (83%)
diff --git a/meta/recipes-devtools/python/python3-dbusmock_0.24.1.bb b/meta/recipes-devtools/python/python3-dbusmock_0.25.0.bb
similarity index 83%
rename from meta/recipes-devtools/python/python3-dbusmock_0.24.1.bb
rename to meta/recipes-devtools/python/python3-dbusmock_0.25.0.bb
index cf272328b3..e64e343a1e 100644
--- a/meta/recipes-devtools/python/python3-dbusmock_0.24.1.bb
+++ b/meta/recipes-devtools/python/python3-dbusmock_0.25.0.bb
@@ -4,7 +4,7 @@ HOMEPAGE = "https://pypi.org/project/python-dbusmock/"
LICENSE = "GPL-3.0"
LIC_FILES_CHKSUM = "file://COPYING;md5=e6a600fd5e1d9cbde2d983680233ad02"
-SRC_URI[sha256sum] = "56d660bd5f5d0edfe8b0eedfbb9b0814a134eb94b46fca16c379dca68be5724f"
+SRC_URI[sha256sum] = "6f4ce7650ecbb022684dc158df720e199635f3a3df75f7020f4fe8f6ff0394db"
PYPI_PACKAGE = "python-dbusmock"
--
2.25.1
next reply other threads:[~2021-12-27 9:09 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-12-27 9:08 Wang Mingyu [this message]
2021-12-27 9:08 ` [OE-core] [PATCH] python3-numpy: upgrade 1.21.4 -> 1.21.5 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=1640596128-22182-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