From: "Mathieu Dubois-Briand" <mathieu.dubois-briand@bootlin.com>
To: <liuyd.fnst@fujitsu.com>, <openembedded-core@lists.openembedded.org>
Subject: Re: [OE-core][PATCH v2] python3-roman-numerals-py: upgrade 3.1.0 -> 4.1.0
Date: Thu, 08 Jan 2026 12:35:34 +0100 [thread overview]
Message-ID: <DFJ6DAKQHTKF.1V0HIXEAL96ME@bootlin.com> (raw)
In-Reply-To: <20260108014101.1974-1-liuyd.fnst@fujitsu.com>
On Thu Jan 8, 2026 at 2:41 AM CET, Yiding Liu (Fujitsu) via lists.openembedded.org wrote:
> 1.Changelog:
> Restore LICENCE.rst in the roman-numerals-py meta-package
> Add some debug assertions for unsafe blocks
>
> 2.Add bbclass python_setuptools_build_meta to solve following error:
> pyproject_hooks._impl.BackendUnavailable: Cannot import 'setuptools.build_meta'
> ERROR Backend 'setuptools.build_meta' is not available.
>
> Signed-off-by: Liu Yiding <liuyd.fnst@fujitsu.com>
> ---
Hi Liu,
Thanks for your patch.
Building btrf seems to be broken by this update:
ERROR: btrfs-tools-6.17.1-r0 do_compile: Execution of '/srv/pokybuild/yocto-worker/qemux86-world-alt/build/build/tmp/work/x86-64-v3-poky-linux/btrfs-tools/6.17.1/temp/run.do_compile.1347185' failed with exit code 1
...
| Extension error!
|
| Versions
| ========
|
| * Platform: linux; (Linux-6.14.5-100.fc40.x86_64-x86_64-with-glibc2.42)
| * Python version: 3.13.11 (CPython)
| * Sphinx version: 9.1.0
| * Docutils version: 0.22.4
| * Jinja2 version: 3.1.6
| * Pygments version: 2.19.2
|
| Last Messages
| =============
|
| None.
|
| Loaded Extensions
| =================
|
| None.
|
| Traceback
| =========
|
| File "/srv/pokybuild/yocto-worker/qemux86-world-alt/build/build/tmp/work/x86-64-v3-poky-linux/btrfs-tools/6.17.1/recipe-sysroot-native/usr/lib/python3.13/site-packages/sphinx/registry.py", line 553, in load_extension
| raise ExtensionError(
| __('Could not import extension %s') % extname, err
| ) from err
| sphinx.errors.ExtensionError: Could not import extension sphinx.builders.latex (exception: No module named 'roman_numerals')
https://autobuilder.yoctoproject.org/valkyrie/#/builders/17/builds/2834
Can you have a look at this issue?
Thanks,
Mathieu
--
Mathieu Dubois-Briand, Bootlin
Embedded Linux and Kernel engineering
https://bootlin.com
next prev parent reply other threads:[~2026-01-08 11:35 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-01-08 1:41 [OE-core][PATCH v2] python3-roman-numerals-py: upgrade 3.1.0 -> 4.1.0 Liu Yiding
2026-01-08 9:46 ` Paul Barker
2026-01-08 9:49 ` Alexander Kanavin
2026-01-08 9:52 ` Paul Barker
2026-01-08 11:35 ` Mathieu Dubois-Briand [this message]
2026-01-09 9:35 ` 回复: " Yiding Liu (Fujitsu)
2026-01-09 10:02 ` 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=DFJ6DAKQHTKF.1V0HIXEAL96ME@bootlin.com \
--to=mathieu.dubois-briand@bootlin.com \
--cc=liuyd.fnst@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