In some situation this may happen in initial builds and should not be treated as an error. Signed-off-by: Alexander Kanavin <alex.kanavin@...> --- modules/buildhistory.py | 11 ++++++++++- 1

The module was doing a lot of things, none of which are necessary: - setting up a separate buildhistory repo for each recipe - running cleansstate before doing initial build - messing about with

Yocto Technical Team Minutes, Engineering Sync, for September 15, 2020 archive: https://docs.google.com/document/d/1ly8nyhO14kDNnFcW2QskANXW3ZT7QwKC5wWVDg9dDH4/edit == disclaimer == Best efforts are

Current Dev Position: YP 3.2 M3 Next Deadline: YP 3.2 M3 Feature Freeze - Now Next Team Meetings: Bug Triage meeting Thursday Sept. 17th at 7:30am PDT (https://zoom.us/j/454367603) Monthly

Thanks Matt!! This solved it. And yes, the branch is thud-l4t-r32.3.1.

Hi Team, Able to create image for using Yocto. After creating the image, I am trying to copy one file using 'wic cp' to 'extt4' partition. while copying i am not getting any error, after flashing the

All, YP M+ or high bugs which moved to a new milestone in WW37 are listed below: Priority Bug ID Short Description Changer Owner Was Became High 13646 runtime tests sometimes can't

All, The below were the owners of enhancements or bugs closed during the last week! Who Count ross@... 2 ydirson@... 2 nickersk@... 1 Grand Total 5 Thanks, Stephen K. Jolley Yocto

All, Below are the lists of open and closed medium or higher Autobuilder Intermittent bugs by the WW created or closed'. Opened Count Closed Count 2019WW47 1 2020WW26 2 2020WW8 1

All, Below is the list as of top 46 bug owners as of the end of WW37 of who have open medium or higher bugs and enhancements against YP 3.2. There are 33 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

In that case, your best bet is to probably write a do_*_append() function into the bbappend recipe so you can jump in after one of the build steps and apply your patch during the appropriate stage.

Hi Chuck,

<eliranl=amazon.com@...> wrote: Which of the meta-tegra branches is it? thud-l4t-r32.3.1? [...] There was an issue with NVIDIA's eqos driver in older BSPs. I know it affected

Are you patching an existing upstream recipe? Or your own recipe? In the former case, you would use a .bbappend recipe. In either case, it all depends on how the service file is generated. If it is

Hi, (since this is a long post, i divided it to sections) TL;DR I have a networking issue in my Yocto dist; Somehow, my ethernet device won't work with systemd-networkd, but will work with

I have a recipe that has a .service file in one of its files directories that I need to patch. I haven’t been able to figure out how to specify the directory of the file that needs to be

Hi all. I'm trying to display a splash screen over a 800x600 display, on Geode LX 800 platform (Geode LX FB or Vesa). I make the image with Gimp and saved in 4 version to try. 800x600 in png 16bit

The issue got resolved after running bitbake -c cleanall binutils. After which it build successfully. -=Srijan Nandi

I am trying to compile binutils-2.32.0-r0 on zeus. I am getting the following error: DEBUG: Executing python function do_unpack DEBUG: Executing python function base_do_unpack DEBUG: Running 'export