public inbox for openembedded-core@lists.openembedded.org
 help / color / mirror / Atom feed
From: "Mathieu Dubois-Briand" <mathieu.dubois-briand@bootlin.com>
To: <alex.kanavin@gmail.com>
Cc: <liezhi.yang@windriver.com>, <openembedded-core@lists.openembedded.org>
Subject: Re: [OE-core] [PATCH v6 0/7] rpm: 4.20.1 -> 6.0.1
Date: Mon, 23 Feb 2026 15:58:17 +0100	[thread overview]
Message-ID: <DGMFHKEHBIY4.24DUCLY3ZXN7N@bootlin.com> (raw)
In-Reply-To: <CANNYZj9DHuV3rmaAsZsPcbZ2ZsbMrNe+keNgVazav=3hUnYQKQ@mail.gmail.com>

On Mon Feb 23, 2026 at 1:27 PM CET, Alexander Kanavin via lists.openembedded.org wrote:
> On Sat, 21 Feb 2026 at 13:15, Mathieu Dubois-Briand via
> lists.openembedded.org
> <mathieu.dubois-briand=bootlin.com@lists.openembedded.org> wrote:
>
>> > I'm sorry about that, but I can't reproduce the error, here are my settings:
>> >
>> > PACKAGE_CLASSES = "package_rpm"
>> > MACHINE = "genericx86"
>> > DISTRO = "poky"
>> >
>> > $ bitbake core-image-sato -cpopulate_sdk
>> >
>> > I checked
>> > tmp/deploy/sdk/poky-glibc-x86_64-core-image-sato-core2-32-genericx86-toolchain-5.3.99+snapshot.target.manifest,
>> > All the required packages are installed correctly:
>> >
>> > flac-dev core2_32 1.5.0
>> > libcomps-dev core2_32 0.1.23
>> > libreadline-dev core2_32 8.3
>> > libogg-dev core2_32 1.3.6
>> > libxml2-dev core2_32 2.15.1
>> > ncurses-dev core2_32 6.5
>> >
>> > I also tested with IMAGE_CLASSES += "testimage", it also works well.
>> >
>> > Do you have more info on how I can reproduce the issue, please?
>>
>> I tried to reproduce it locally yesterday, and I had the same issue: the
>> failure did not reproduce. Yet I tried again to apply your patches and
>> got a similar error on the autobuilder.
>>
>> https://autobuilder.yoctoproject.org/valkyrie/#/builders/19/builds/3218
>>
>> I will try to investigate this next week.
>
> Note that the autobuilder enables the
> 'core/yocto-autobuilder/autobuilder' fragment, which contains
> significant SDK tweaks:
>
> SDK_EXT_TYPE = 'minimal'
> SDK_INCLUDE_TOOLCHAIN = '1'
> ESDK_LOCALCONF_REMOVE:append = 'BB_HASHSERVE'
> SDK_TOOLCHAIN_LANGS += 'go rust'
>
> I suspect the above may be enough to trigger the issue (or maybe if
> you enable the whole fragment).
>
> Alex

Of course! It was definitely the missing config, thanks!

So it was reproduced locally, with basically the template local.conf
and the following added lines:
PACKAGE_CLASSES = "package_rpm"
OE_FRAGMENTS += 'machine/qemux86 distro/poky'
OE_FRAGMENTS += 'core/yocto-autobuilder/autobuilder'

Thanks,
Mathieu

-- 
Mathieu Dubois-Briand, Bootlin
Embedded Linux and Kernel engineering
https://bootlin.com



  reply	other threads:[~2026-02-23 14:58 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-02-18 12:22 [PATCH v6 0/7] rpm: 4.20.1 -> 6.0.1 liezhi.yang
2026-02-18 12:22 ` [PATCH v6 1/7] package_rpm.bbclass: Drop external dependency generator to support rpm 6 liezhi.yang
2026-02-18 12:22 ` [PATCH v6 2/7] package_rpm.bbclass: Define _lib and _libdir for rpmbuild liezhi.yang
2026-02-18 12:22 ` [PATCH v6 3/7] lib/oe/package.py: Don't add ldconfig_postinst_fragment for glibc or musl liezhi.yang
2026-02-18 12:22 ` [PATCH v6 4/7] glib/python3/acl: Add pkgconfig to RDEPENDS liezhi.yang
2026-02-18 12:22 ` [PATCH v6 5/7] lib/oe/package.py: Don't redirect stderr liezhi.yang
2026-02-18 12:22 ` [PATCH v6 6/7] target-sdk-provides-dummy: Add pkg-config to DUMMYPROVIDES liezhi.yang
2026-02-18 12:22 ` [PATCH v6 7/7] rpm: 4.20.1 -> 6.0.1 liezhi.yang
2026-02-18 17:50 ` [OE-core] [PATCH v6 0/7] " Mathieu Dubois-Briand
2026-02-20  5:27   ` Robert Yang
2026-02-21 12:15     ` Mathieu Dubois-Briand
2026-02-23 12:27       ` Alexander Kanavin
2026-02-23 14:58         ` Mathieu Dubois-Briand [this message]
2026-02-26 16:00           ` Robert Yang
2026-02-27  9:16             ` Mathieu Dubois-Briand
2026-02-28  3:53               ` Robert Yang
2026-02-28  8:01                 ` Robert Yang

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=DGMFHKEHBIY4.24DUCLY3ZXN7N@bootlin.com \
    --to=mathieu.dubois-briand@bootlin.com \
    --cc=alex.kanavin@gmail.com \
    --cc=liezhi.yang@windriver.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