From: wangmy@fujitsu.com
To: openembedded-core@lists.openembedded.org
Cc: Wang Mingyu <wangmy@fujitsu.com>
Subject: [OE-core] [PATCH 18/26] python3-setuptools-rust: upgrade 1.10.1 -> 1.10.2
Date: Wed, 9 Oct 2024 13:49:07 +0800 [thread overview]
Message-ID: <1728452955-25051-18-git-send-email-wangmy@fujitsu.com> (raw)
In-Reply-To: <1728452955-25051-1-git-send-email-wangmy@fujitsu.com>
From: Wang Mingyu <wangmy@fujitsu.com>
Changelog:
Fix deprecation warning from use of wheel.bdist_wheel.
Signed-off-by: Wang Mingyu <wangmy@fujitsu.com>
---
...uptools-rust_1.10.1.bb => python3-setuptools-rust_1.10.2.bb} | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
rename meta/recipes-devtools/python/{python3-setuptools-rust_1.10.1.bb => python3-setuptools-rust_1.10.2.bb} (90%)
diff --git a/meta/recipes-devtools/python/python3-setuptools-rust_1.10.1.bb b/meta/recipes-devtools/python/python3-setuptools-rust_1.10.2.bb
similarity index 90%
rename from meta/recipes-devtools/python/python3-setuptools-rust_1.10.1.bb
rename to meta/recipes-devtools/python/python3-setuptools-rust_1.10.2.bb
index d2881e9101..a58d57ac70 100644
--- a/meta/recipes-devtools/python/python3-setuptools-rust_1.10.1.bb
+++ b/meta/recipes-devtools/python/python3-setuptools-rust_1.10.2.bb
@@ -9,7 +9,7 @@ BUGTRACKER = "https://github.com/PyO3/setuptools-rust/issues"
LICENSE = "MIT"
LIC_FILES_CHKSUM = "file://LICENSE;md5=011cd92e702dd9e6b1a26157b6fd53f5"
-SRC_URI[sha256sum] = "d79035fc54cdf9342e9edf4b009491ecab06c3a652b37c3c137c7ba85547d3e6"
+SRC_URI[sha256sum] = "5d73e7eee5f87a6417285b617c97088a7c20d1a70fcea60e3bdc94ff567c29dc"
PYPI_PACKAGE = "setuptools_rust"
--
2.34.1
next prev parent reply other threads:[~2024-10-09 5:49 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-10-09 5:48 [OE-core] [PATCH 01/26] bash: upgrade 5.2.32 -> 5.2.37 wangmy
2024-10-09 5:48 ` [OE-core] [PATCH 02/26] dhcpcd: upgrade 10.0.10 -> 10.1.0 wangmy
2024-10-09 5:48 ` [OE-core] [PATCH 03/26] erofs-utils: upgrade 1.8.1 -> 1.8.2 wangmy
2024-10-09 5:48 ` [OE-core] [PATCH 04/26] fribidi: upgrade 1.0.15 -> 1.0.16 wangmy
2024-10-09 5:48 ` [OE-core] [PATCH 05/26] git: upgrade 2.46.1 -> 2.47.0 wangmy
2024-10-09 5:48 ` [OE-core] [PATCH 06/26] gtk4: upgrade 4.16.1 -> 4.16.3 wangmy
2024-10-09 5:48 ` [OE-core] [PATCH 07/26] harfbuzz: upgrade 9.0.0 -> 10.0.1 wangmy
2024-10-09 5:48 ` [OE-core] [PATCH 08/26] libproxy: upgrade 0.5.8 -> 0.5.9 wangmy
2024-10-09 5:48 ` [OE-core] [PATCH 09/26] libsdl2: upgrade 2.30.7 -> 2.30.8 wangmy
2024-10-09 5:48 ` [OE-core] [PATCH 10/26] libuv: upgrade 1.48.0 -> 1.49.0 wangmy
2024-10-09 5:49 ` [OE-core] [PATCH 11/26] ltp: upgrade 20240524 -> 20240930 wangmy
2024-10-09 5:49 ` [OE-core] [PATCH 12/26] msmtp: upgrade 1.8.26 -> 1.8.27 wangmy
2024-10-09 5:49 ` [OE-core] [PATCH 13/26] mtools: upgrade 4.0.44 -> 4.0.45 wangmy
2024-10-09 5:49 ` [OE-core] [PATCH 14/26] python3-dbusmock: upgrade 0.32.1 -> 0.32.2 wangmy
2024-10-09 5:49 ` [OE-core] [PATCH 15/26] python3-hypothesis: upgrade 6.112.1 -> 6.112.4 wangmy
2024-10-09 5:49 ` [OE-core] [PATCH 16/26] python3-pefile: upgrade 2023.2.7 -> 2024.8.26 wangmy
2024-10-09 5:49 ` [OE-core] [PATCH 17/26] python3-pycryptodome(x): upgrade 3.20.0 -> 3.21.0 wangmy
2024-10-09 5:49 ` wangmy [this message]
2024-10-09 5:49 ` [OE-core] [PATCH 19/26] python3-spdx-tools: upgrade 0.8.2 -> 0.8.3 wangmy
2024-10-09 5:49 ` [OE-core] [PATCH 20/26] python3-sphinx-rtd-theme: upgrade 2.0.0 -> 3.0.0 wangmy
2024-10-09 5:49 ` [OE-core] [PATCH 21/26] shaderc: upgrade 2024.2 -> 2024.3 wangmy
2024-10-09 5:49 ` [OE-core] [PATCH 22/26] ttyrun: upgrade 2.34.0 -> 2.35.0 wangmy
2024-10-09 5:49 ` [OE-core] [PATCH 23/26] wireless-regdb: upgrade 2024.07.04 -> 2024.10.07 wangmy
2024-10-09 5:49 ` [OE-core] [PATCH 24/26] xkeyboard-config: upgrade 2.42 -> 2.43 wangmy
2024-10-09 5:49 ` [OE-core] [PATCH 25/26] xwayland: upgrade 24.1.2 -> 24.1.3 wangmy
2024-10-09 5:49 ` [OE-core] [PATCH 26/26] xz: upgrade 5.6.2 -> 5.6.3 wangmy
2024-10-09 9:57 ` [OE-core] [PATCH 01/26] bash: upgrade 5.2.32 -> 5.2.37 Alexander Kanavin
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=1728452955-25051-18-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