All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Antonin Godard" <antonin.godard@bootlin.com>
To: <richard.purdie@linuxfoundation.org>,
	"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 15:13:25 +0200	[thread overview]
Message-ID: <DKS3H5V66DML.S0T04UJ1AEW4@bootlin.com> (raw)
In-Reply-To: <bd1815271e8babc6248563bb7b8da5adecfe55a0.camel@linuxfoundation.org>

Hi,

On Tue Aug 18, 2026 at 2:18 PM CEST, Richard Purdie via lists.openembedded.org wrote:
[...]
>> 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...

You're right. I didn't realise the html module was packaged separately
(python3-html). Adding the runtime dependency fixes the issue for me. Thanks! v2
incoming.

Antonin


      reply	other threads:[~2026-08-18 13:13 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
2026-08-18 13:13       ` Antonin Godard [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=DKS3H5V66DML.S0T04UJ1AEW4@bootlin.com \
    --to=antonin.godard@bootlin.com \
    --cc=mathieu.dubois-briand@bootlin.com \
    --cc=openembedded-core@lists.openembedded.org \
    --cc=richard.purdie@linuxfoundation.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 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.