From: "Mathieu Dubois-Briand" <mathieu.dubois-briand@bootlin.com>
To: <wangmy@fujitsu.com>, <openembedded-core@lists.openembedded.org>
Subject: Re: [OE-core] [PATCH 12/17] python3-pycparser: upgrade 2.23 -> 3.0
Date: Tue, 27 Jan 2026 16:42:42 +0100 [thread overview]
Message-ID: <DFZHIVF68NIV.KQ0S80RPIHUF@bootlin.com> (raw)
In-Reply-To: <20260126123844.1052-1-wangmy@fujitsu.com>
On Mon Jan 26, 2026 at 1:38 PM CET, wangmy via lists.openembedded.org wrote:
> From: Wang Mingyu <wangmy@fujitsu.com>
>
> Signed-off-by: Wang Mingyu <wangmy@fujitsu.com>
> ---
Hi Wang,
Thanks for your patch.
It looks like we have some warnings during the build:
WARNING: python3-pycparser-native-3.0-r0 do_check_backend: QA Issue: inherits setuptools3 but has pyproject.toml with setuptools.build_meta, use the correct class [pep517-backend]
https://autobuilder.yoctoproject.org/valkyrie/#/builders/73/builds/2989
Can you update the recipe?
Thanks,
Mathieu
--
Mathieu Dubois-Briand, Bootlin
Embedded Linux and Kernel engineering
https://bootlin.com
prev parent reply other threads:[~2026-01-27 15:42 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-01-26 12:38 [OE-core] [PATCH 12/17] python3-pycparser: upgrade 2.23 -> 3.0 Wang Mingyu
2026-01-26 12:38 ` [OE-core] [PATCH 13/17] python3-pyparsing: upgrade 3.3.1 -> 3.3.2 Wang Mingyu
2026-01-26 12:38 ` [OE-core] [PATCH 14/17] python3-sphinx-rtd-theme: upgrade 3.0.2 -> 3.1.0 Wang Mingyu
2026-01-26 12:38 ` [OE-core] [PATCH 15/17] python3-uv-build: upgrade 0.9.18 -> 0.9.26 Wang Mingyu
2026-01-26 12:38 ` [OE-core] [PATCH 16/17] python3-wheel: upgrade 0.46.1 -> 0.46.3 Wang Mingyu
2026-01-28 16:44 ` Mathieu Dubois-Briand
2026-01-29 8:06 ` Mingyu Wang (Fujitsu)
2026-02-03 9:09 ` Mingyu Wang (Fujitsu)
2026-02-03 9:13 ` Mingyu Wang (Fujitsu)
2026-02-09 13:57 ` Alexander Kanavin
2026-01-26 12:38 ` [OE-core] [PATCH 17/17] python3-yamllint: upgrade 1.37.1 -> 1.38.0 Wang Mingyu
2026-01-27 15:42 ` Mathieu Dubois-Briand [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=DFZHIVF68NIV.KQ0S80RPIHUF@bootlin.com \
--to=mathieu.dubois-briand@bootlin.com \
--cc=openembedded-core@lists.openembedded.org \
--cc=wangmy@fujitsu.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox