ping :) Alex

Thanks all for valuable inputs. Issue solved +1

Is there a way around this ?

Current Dev Position: YP 3.3 M1 development Next Deadline: 7th December 2020 YP 3.3 M1 build Next Team Meetings: Bug Triage meeting Thursday Nov. 19th at 7:30am PDT

On a related note, the do_install reference in the manual gives some advice on how to use cp and tar without contaminating the build. The relevant part: Safe methods for installing files include the

Hi Team, I've built OS for rpi3 using dunfell yocto. I've also generated SDK for the same, for that I've added these info in my local.conf file- TOOLCHAIN_TARGET_TASK_append = " python3-dev kernel-dev

On Mon, Nov 16, 2020 at 11:43 PM chuck kamas via lists.yoctoproject.org <chuckkamas=yahoo.com@...> wrote: what does /boot/config.txt look like on raspbian and yocto built images

Hi all, I have been spinning my wheels for two days trying to discover how to enable MMC1 on a CM3. This is the one on GPIO22-27. I can boot Rasbian on the CM3 and it inits the MMC1 and its pins

All, The below were the owners of enhancements or bugs closed during the last week! Who Count steve@... 1 chee.yang.lee@... 1 randy.macleod@... 1 richard.purdie@... 1 Grand

All, Below is the list as of top 50 bug owners as of the end of WW46 of who have open medium or higher bugs and enhancements against YP 3.3. There are 111 possible work days left until the final

All, The triage team is starting to try and collect up and classify bugs which a newcomer to the project would be able to work on in a way which means people can find them. They're being listed on

https://github.com/webOS-ports/meta-webos-ports/commit/9fd17a67cdbed92df13a14b002a189b4c6c2d442 is an example where it triggers this error, but doesn't trigger the more common host-user-contaminated

Hi Alex, just did it: https://lists.openembedded.org/g/openembedded-core/message/144671 -- Cheers! Loic

Some ideas what can be the source of that. This recipe is basically just copying files from archive to final rootfs without any special processing or so. BR, marek

This means the recipe is having host contamination (where the UID of the user doing the build is leaking into the file system).

Hi, I'm bumping my project based on zeus to dunfell. I've update all layers and in one of my recipes I'm seeing following issue (not see on zeus at all): WARNING: cv-my-test-1.0-r0 do_package:

hi Vasyl, Ah, you're right. It was possible with the previous docs, but not anymore. With the Sphinx based docs the whole Yocto Project docs is just "one set", not a collection of 'manuals'. So

From: Ross Burton <ross.burton@...> Signed-off-by: Ross Burton <ross.burton@...> --- config.py | 5 ++--- 1 file changed, 2 insertions(+), 3 deletions(-) diff --git a/config.py

From: Ross Burton <ross.burton@...> Signed-off-by: Ross Burton <ross.burton@...> --- config.json | 3 +-- 1 file changed, 1 insertion(+), 2 deletions(-) diff --git a/config.json

From: Ross Burton <ross.burton@...> Signed-off-by: Ross Burton <ross.burton@...> --- config.json | 3 +-- 1 file changed, 1 insertion(+), 2 deletions(-) diff --git a/config.json