It's hard to say what happens if we can't see your recipes. Can you publish them? Alex

I did as Richard suggested, It worked as expected now feature-public.bb or feature-private.bb: SRC_URI = "git://public or git://private" PROVIDES += "virtual/feature" RPROVIDES:${PN} += "

Inside the do_install I copy some files but it seems that bitbake set those files in the RDEPENS. In the log during the do_root_fs I see: Requires(post): ... mylib.so After that the commands fail with

Then you need to check the output of 'env' a) when you start the shell b) when you use oe-init-build-env and figure out how the incorrect variable gets into the environment. Are you using

fetcher will try to get versions of recipes during parse phase and if your recipes are using AUTOREV they will try to poke at git server for latest commit SHA are you using AUTOREV by chance ?

make[2]: *** No rule to make target '../rust/target/arm-poky-linux-gnueabi/release/libsuricata.a', needed by 'suricata' Signed-off-by: Armin Kuster <akuster808@...> ---

"virtual" entries only work in PROVIDES and PREFERRED_PROVIDER, not in the runtime version of the variable. Cheers, Richard

Hi, There is a package with two versions, private and public. But when I use the PREFERRED_RPROVIDER to select the public version, bitbake still tries fetch the private one, and then bitabke

Hello, you probably need to exit the shell and then restart it and re-initialize your environment (with oe-init-build-env), as it contains the obsolete variable. Alex

Hellow everyone, this is Yan. I am new to Yocto Project, still, I am learning. There is a question, when I bitbaked my image I found this ERROR: yanxk@yanxk-Ubuntu:~/Yocto/poky/build$ bitbake

merged

merged

Merged.

Hi all, I have taken on myself a task to write a custom Yocto-based image for Nvidia Xavier which poses somewhat of a difficult task. After few videos on Youtube and some documentation, I started

The changes to split classes into global vs. image specific contexts has broken the inclusion of `wine` and `wineserver` host tools for testing MinGW SDKs. This is because testsdk is an image specific

it is part of systemd recipe if your distro is based on systemd. In that case, you can write a bbappend where you define do_install:append() and delete it from staging area before it gets packaged

Wiki: https://wiki.yoctoproject.org/wiki/Bug_Triage Attendees: Steve Sakoman, Joshua Watt, Randy Macleod, Richard Purdie, Aryaman, Bruce Ashfield, Michael Opdenacker, Alexandre

Hello, I am aware of a new build failure with suricata. I think it related to the glibc update. https://errors.yoctoproject.org/Errors/Build/150774/ I will have limited time to look into this in

From: Mingli Yu <mingli.yu@...> Fixes: WARNING: samhain-standalone-4.4.9-r0 do_package_qa: QA Issue: File /usr/share/doc/samhain-standalone/scripts/samhain.ebuild-light in package

Hello all, Intel and WR YP QA is planning for QA execution for YP build yocto-4.0.3.rc1. We are planning to execute following tests for this cycle: OEQA-manual tests for following module: 1.