- correctly save files into sstate - fix: ERROR: Task linux-dummy.do_fetch attempted to execute unexpectedly Signed-off-by: Andrej Valek <andrej.valek@...> ---

I wouldn't recommend this in a core recipe, since there may be task dependencies, or someone, somewhere extending those tasks. If they aren't triggering the problem you are fixing, I'd leave them

I don't think "CLOSED" is a good choice to use in the core metadata. The usual way to handle recipes like this which don't require external source code is to say that they have the same license as the

- refactor kernel dummy recipe - remove unneeded COPYING.GPL file -> change license to close - remove unneeded tasks (fetch, unpack, pack) - do not run unneeded tasks, but keep deps (configure,

i have not really spent time looking into this

Dear all, I have 4 different topics on which I can't find a correct answer on internet. I am developing a new system base on the Raspberrypi CM3+ with our custom board. I am using Yocto with the

Signed-off-by: Adrian Ratiu <adrian.ratiu@...> --- .../tpm2-pkcs11/tpm2-pkcs11_1.4.0.bb | 25 +++++++++++++++++-- 1 file changed, 23 insertions(+), 2 deletions(-) diff --git

Maybe related to this: meta/conf/distro/include/default-distrovars.inc # The CONNECTIVITY_CHECK_URIS are used to test whether we can succesfully # fetch from the network (and warn you if

simply adding a recipe to your layer is not sufficient ... you need to specifically say you want a package added to your image with, perhaps, adding the line: IMAGE_INSTALL_append = " <package>

Hi, can anyone please guide me on adding json module to my python library in yocto. I had download .bb file from OE Layer and placed it under recipe-devtool/python folder, but it is not including to

The issue was located. I had overridden to the local path of one recipe via "devtool modify -n <my_recipe>" /my/local/path and during parsing it hangs at "Inheriting

Since today i encountered issue in the topic. I had this issue before when i forgot to turn on vpn (somehow parsing depends on it). But today is everything is OK and i wonder what went wrong. More

Hello Khem, I was, that you were trying to figure you, what’s going wrong with “linux-dummy” kernel in eSDK case. Did you or somebody else find something? I have the same problem as

Ok I've found a solution by myself. Basically I just used the trick showed in the Technical FAQ and put a bunch of install commands in the do_install task. Now the only problem I have is that the

All, YP M+ or high bugs which moved to a new milestone in WW47 are listed below: Priority Bug ID Short Description Changer Owner Was Became Medium+ 13338 SDK build fails if image contains

All, The below were the owners of enhancements or bugs closed during the last week! Who Count richard.purdie@... 5 randy.macleod@... 4 mhalstead@... 1 ross@... 1 Grand Total 11 Thanks,

All, Below is the list as of top 50 bug owners as of the end of WW47 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

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. 26th at 7:30am PDT

Hi Vijay Reading and following the section about "Writing a New Recipe" in the manual is probably a good starting