Greetings ! I am having requirement of integrating Opentelemetry in Yocto Zeus . Requesting your suggestions/procedure for integrating Opentelemetry in Yocto Zeus . Thanks in advance

Hi all, I'm currently using an additional layer and image to differentiate between a release and development build (enabling NFS, SSH, root login, etc.). To create a development build, I manually add

Hello All, I was testing my core-image-minimal with test-suit and getting error like "need terminal to enter password and set-up tap interface" i am getting few error so i am not able to test my image

Reviewed-by: Michael Opdenacker <michael.opdenacker@...> Indeed, it should be applied right after the latest pull request from master-next is applied. Cheers Michael. -- Michael Opdenacker, Bootlin Em

Build and test core-image-full-cmdline with the linux-yocto-rt kernel, adding the new rt test to verify that the kernel is actually the PREEMPT_RT version expected. Signed-off-by: Ross Burton <ross.bu

Greetings ! I am working on NXP's i.MX6UL SoC and I have successfully built a Read-only Rootfile system through Yocto. Now I am having a requirement of making only "/etc" as Read & Writable . So , Can

From: Michael Opdenacker <michael.opdenacker@...> From: Quentin Schulz <quentin.schulz@...> In order to maintain one less file, let's auto-generate the releases.rst file which contains a link for each

Note: this update fails on x32 with | configure: error: unrecognized GNU build triplet linux-gnux32 This time I want to put my foot down and suggest that we just drop the whole x32 variant from the au

I am using the AM572x evaluation module with the TI SDK, which uses the linaro toolchain. I am trying to enable UTF-8 so that I can use tmux. I am enabling it using the follow method: unset IMAGE_LING

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

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

We are moving the hash equivalence server to dedicated servers. As part of the change we need to change the domain. Please update any BB_HASHSERVE_UPSTREAM variables from "typhoon.yocto.io:8687" to "h

From: Michael Opdenacker <michael.opdenacker@...> This allows to switch to a more recent of Sphinx which will generate warnings with old versions of docs. This way, it's not immediately necessary to p

Current Dev Position: YP 4.1 M3 Next Deadline: 22nd August 2022 YP 4.1 M3 Build Next Team Meetings: Bug Triage meeting Thursday July 21st 7:30 am PDT (https://zoom.us/j/454367603?pwd=ZGxoa2ZXL3FkM3Y0b

This is optional, enabled by default, and allows easy extraction of patches and other information to one's local disk (no need to go over individual maintainer emails). Signed-off-by: Alexander Kanavi

MIMEBase should not be used directly and results in sending raw binary data without encoding it with base64. Signed-off-by: Alexander Kanavin <alex@...> --- modules/utils/emailhandler.py | 6 ++---- 1

Hi Quentin That's brilliant, thanks a lot! Just a few comments below... Don't forget to add your name to the authors at the beginning of the script and what the script does now. Thanks again! Cheers M

Master branch of the yocto-docs now autogenerates the releases.rst file and the file therefore does not exist anymore. Signed-off-by: Quentin Schulz <foss+yocto@...> --- scripts/run-docs-build | 2 +-

From: Quentin Schulz <quentin.schulz@...> `git checkout <pathspec>` without <tree-ish> only undo the changes made to pathspec compared to HEAD. It is not guaranteed that HEAD is on latest commit of ma

From: Quentin Schulz <quentin.schulz@...> In order to maintain one less file, let's auto-generate the releases.rst file which contains a link for each release ever released. This gets auto-generated b