From: Richard Purdie <richard.purdie@linuxfoundation.org>
To: antonin.godard@bootlin.com,
Mathieu Dubois-Briand <mathieu.dubois-briand@bootlin.com>,
openembedded-core@lists.openembedded.org
Cc: Thomas Petazzoni <thomas.petazzoni@bootlin.com>
Subject: Re: [OE-core] [PATCH] python3-pygments: update 2.20.0 -> 2.21.0
Date: Tue, 18 Aug 2026 13:18:12 +0100 [thread overview]
Message-ID: <bd1815271e8babc6248563bb7b8da5adecfe55a0.camel@linuxfoundation.org> (raw)
In-Reply-To: <DKRWWL8NYSSQ.2TTCOYTRP2AO7@bootlin.com>
On Tue, 2026-08-18 at 10:04 +0200, Antonin Godard via lists.openembedded.org wrote:
> Hi,
>
> On Tue Aug 18, 2026 at 7:37 AM CEST, Mathieu Dubois-Briand wrote:
> > On Mon Aug 17, 2026 at 12:13 PM CEST, Antonin Godard via lists.openembedded.org wrote:
> > > One notable change from this update is the addition of a Bitbake lexer,
> > > which will allow us to do proper Bitbake syntax coloring in our
> > > documentation.
> > >
> > > Full list of changes:
> > > https://github.com/pygments/pygments/releases/tag/2.21.0
> > >
> > > Tested using this version for the documentation with our
> > > buildtools-docs-tarball recipe.
> > >
> > > Signed-off-by: Antonin Godard <antonin.godard@bootlin.com>
> > > ---
> >
> > Hi Antonin,
> >
> > Thanks for your patch.
> >
> > It looks like this upgrade might be breaking some ptests, for a lot of
> > python recipes:
> >
> > Failed ptests:
> > {'python3-click': 'START: ptest-runner\n'
> > ...
> > Failed ptests:
> > {'python3-xmltodict': 'START: ptest-runner\n'
> > ...
> > Failed ptests:
> > {'python3-webcolors': 'START: ptest-runner\n'
> > ...
> > Failed ptests:
> > {'python3-wcwidth': 'START: ptest-runner\n'
> > ...
> > Failed ptests:
> > {'python3-uritools': 'START: ptest-runner\n'
> > ...
> >
> > https://autobuilder.yoctoproject.org/valkyrie/#/builders/56/builds/2181
> > https://autobuilder.yoctoproject.org/valkyrie/#/builders/61/builds/4294
> > https://autobuilder.yoctoproject.org/valkyrie/#/builders/73/builds/4311
> > https://autobuilder.yoctoproject.org/valkyrie/#/builders/109/builds/986
> > https://autobuilder.yoctoproject.org/valkyrie/#/builders/110/builds/967
> >
> > Can you have a look at the issues?
>
> I don't really understand it yet, the issue is always the same it seems:
>
> '"/usr/lib/python3.14/site-packages/pygments/util.py", '
> 'line 13, in <module>\n'
> ' import html\n'
> "ModuleNotFoundError: No module named 'html'\n"
>
> Yet the html module is provided by python3, and does show up in
> python3-pygments' sysroot when I build it:
>
> tmp/work/cortexa57-oe-linux/python3-pygments/2.21.0/recipe-sysroot/usr/lib/python3.14/html/
Those are ptest runtime errors (i.e. an image booted under qemu) so
probably a missing RDEPENDS on a python module somewhere...
Cheers,
Richard
next prev parent reply other threads:[~2026-08-18 12:18 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-08-17 10:13 [PATCH] python3-pygments: update 2.20.0 -> 2.21.0 Antonin Godard
2026-08-18 5:37 ` [OE-core] " Mathieu Dubois-Briand
2026-08-18 8:04 ` Antonin Godard
2026-08-18 12:18 ` Richard Purdie [this message]
2026-08-18 13:13 ` Antonin Godard
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=bd1815271e8babc6248563bb7b8da5adecfe55a0.camel@linuxfoundation.org \
--to=richard.purdie@linuxfoundation.org \
--cc=antonin.godard@bootlin.com \
--cc=mathieu.dubois-briand@bootlin.com \
--cc=openembedded-core@lists.openembedded.org \
--cc=thomas.petazzoni@bootlin.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