A build flagged for QA (yocto-3.1.14.rc1) was completed on the autobuilder and is available at: https://autobuilder.yocto.io/pub/releases/yocto-3.1.14.rc1 Build hash information: bitbake:

Thanks, Alex! That was it. The script that started the matchbox-terminal is /usr/bin/mini-x-session. I just edited this file and commented out the terminal line and another line that was setting my

Hi all. The KCONF_AUDIT_LEVEL variable must be setup in a .conf file or I can change it in a recipe? I try to understand why my file defconfig is not used my kernel configurator MZ

In Zeus I have a recipe that installs the file (a u-boot boot.scr for me): install -m 0644 boot.scr ${DEPLOYDIR} Make sure the recipe is included in your image. Then in my machine

Hello @Nicolas @Erik @Khem, Update from my side: After following some discussion from other posts, I added "config" file. ~/.ssh/config: Host git.example.com HostName git.example.com User

The logs reveal that 'packagegroup-core-x11 packagegroup-core-x11-base packagegroup-core-x11-xserver' are all installed. x11-base pulls in recipes-graphics/mini-x-session/mini-x-session_0.1.bb which

Hi all, This is the full report for yocto-3.5_M2.rc6: https://git.yoctoproject.org/cgit/cgit.cgi/yocto-testresults-contrib/tree/?h=intel-yocto-testresults ======= Summary ======== No high

Thanks, Alex. The log file is attached. By the way, I'd be happy with a solution that involves changing a file on the target system after the Yocto build is complete. The fix doesn't need to be in

Please share the log.do_rootfs for your image, otherwise it's difficult to say why the terminal ends up being there and gets autostarted. Alex

Hello Yocto Community - I am using Yocto to build a core-image-minimal image for Intel hardware. When the system boots, it automatically starts a matchbox-terminal as root. This is a huge security

see https://github.com/lkrg-org/lkrg Support new stable and mainline kernels 5.14 to at least 5.16-rc* Support new longterm kernels 5.4.118+, 4.19.191+, 4.14.233+ update SRC_URI as location

Hello everyone, I need to put the boot.sh file in the build/deploy/images/$IMAGE_NAME/ directory during the build, how can I do this using the yocto build system?

dstat was removed from meta-oe. Signed-off-by: Armin Kuster <akuster808@...> --- meta-tpm/recipes-tpm2/tpm2-pkcs11/tpm2-pkcs11_1.7.0.bb | 2 +- 1 file changed, 1 insertion(+), 1

fixes: packagegroup-security-tpm2-1.0-r0 do_package_write_rpm: An allarch packagegroup shouldn't depend on packages which are dynamically renamed (libtss2-tcti-device to

Hi list. I solved my problem working with distutils parameteres inside myapp.bb recipe Mauro

Hi, If you can come up with a reasonably simple reproducer and it fails on a supported branch: https://wiki.yoctoproject.org/wiki/Releases then we'd appreciate if if you could report the bug in

Hi, Adding that line results in an error: ERROR: Nothing RPROVIDES 'syslog' (but /yocto/poky-dunfell/meta/recipes-core/packagegroups/packagegroup-core-boot.bb,

Hi Paul, Try adding: VIRTUAL-RUNTIME_base-utils-syslog = "syslog" as shown on: https://git.yoctoproject.org/poky/tree/meta-poky/conf/local.conf.sample.extended#n371 I would expect that since you

yeah something like that works, we use it for yoe which always uses container to build see https://github.com/YoeDistro/yoe-distro/blob/master/envsetup.sh#L528-L541