From: Bartosz Golaszewski <brgl@bgdev.pl>
To: Khem Raj <raj.khem@gmail.com>,
Bruce Ashfield <bruce.ashfield@gmail.com>,
openembedded-devel@lists.openembedded.org
Cc: Bartosz Golaszewski <bartosz.golaszewski@linaro.org>
Subject: [meta-python][PATCH 2/2] python3-gpiod: update to v2.0
Date: Thu, 2 Mar 2023 16:44:43 +0100 [thread overview]
Message-ID: <20230302154443.349083-3-brgl@bgdev.pl> (raw)
In-Reply-To: <20230302154443.349083-1-brgl@bgdev.pl>
From: Bartosz Golaszewski <bartosz.golaszewski@linaro.org>
The final libgpiod v2.0 release is out so update the recipe.
Signed-off-by: Bartosz Golaszewski <bartosz.golaszewski@linaro.org>
---
.../python/{python3-gpiod_2.0-rc3.bb => python3-gpiod_2.0.bb} | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
rename meta-python/recipes-devtools/python/{python3-gpiod_2.0-rc3.bb => python3-gpiod_2.0.bb} (95%)
diff --git a/meta-python/recipes-devtools/python/python3-gpiod_2.0-rc3.bb b/meta-python/recipes-devtools/python/python3-gpiod_2.0.bb
similarity index 95%
rename from meta-python/recipes-devtools/python/python3-gpiod_2.0-rc3.bb
rename to meta-python/recipes-devtools/python/python3-gpiod_2.0.bb
index 6af1542bf..18cf8ae8b 100644
--- a/meta-python/recipes-devtools/python/python3-gpiod_2.0-rc3.bb
+++ b/meta-python/recipes-devtools/python/python3-gpiod_2.0.bb
@@ -12,7 +12,7 @@ require recipes-support/libgpiod/libgpiod-src.inc
SRC_URI += "file://run-ptest"
-SRC_URI[sha256sum] = "1d1756d465525deb668526571dc6ed7e08f7b8e7745b10fc028208a22fb7adf8"
+SRC_URI[sha256sum] = "f74cbf82038b3cb98ebeb25bce55ee2553be28194002d2a9889b9268cce2dd07"
S = "${WORKDIR}/libgpiod-2.0/bindings/python"
inherit setuptools3 ptest
--
2.37.2
prev parent reply other threads:[~2023-03-02 15:45 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-02 15:44 [meta-oe][PATCH 0/2] libgpiod: update library and python recipes to v2.0 Bartosz Golaszewski
2023-03-02 15:44 ` [meta-oe][PATCH 1/2] libgpiod: update " Bartosz Golaszewski
2023-03-02 15:44 ` Bartosz Golaszewski [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=20230302154443.349083-3-brgl@bgdev.pl \
--to=brgl@bgdev.pl \
--cc=bartosz.golaszewski@linaro.org \
--cc=bruce.ashfield@gmail.com \
--cc=openembedded-devel@lists.openembedded.org \
--cc=raj.khem@gmail.com \
/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.