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

On 2022-01-28 12:02, Randy MacLeod wrote: That is, can you not package each moduleA as moduleA and moduleA-private using Yocto's packaging mechanism with the *3.h files being

On 2022-01-24 13:04, Praveen wrote: Hi Praveen, I'm not aware of anyone else doing that. For libraries/recipes, you could just omit certain packages from the eSDK

I use my own Dockerfile based on crops/poky where I do the following, which might be helpful if you also use this. It sets up the config changes in /etc/skel/ since it creates users "on the fly"

That's pretty much what I use. I do something similar, my "problem" was that ssh needs the .ssh/known_hosts file with a matching entry in addition to your key/agent, but mounting the .ssh folder was

Hi, I use the following options within the Docker run command: -v $SSH_AUTH_SOCK:/ssh.socket \ -e SSH_AUTH_SOCK=/ssh.socket \ Furthermore, I had to mount the .ssh folder into the container to

Hi Nicolas, Thanks for your answer. That's great. Even I am building inside a docker container. I tried with creating a "config" file in .ssh directory. But I still have same issue. Can you please let

I use almost the same, just without submodules. SRC_URI = "git://git@...:1234/group/project.git;protocol=ssh" It should "just work" if ssh is able to find your key. I often build in a

Checkout the branches from the same repo into two different directories. Yes this is unusual, and slightly confusing. But that way the branches can be maintained and included into builds

How would one use new version of both go and say kernel in a project

Michael, Would it be possible to create 2 additional branches in the meta-lts-mixins repository at https://git.yoctoproject.org/meta-lts-mixins/ called "dunfell/go" and also "dunfell/docker" and

<alex.kanavin@...> wrote: this could be an independent layer too.

A question specifically to Denys, how can I actually get this into the mixin repo, and have commit rights to the branch? We've tested this quite well in private, and there are further enhancements

Hello Bruce, I chose the variant based on SRC_URI, but used KERNEL_CONFIG_URI because I got endless recursion between SRC_URI and KERNEL_FEATURES in the kernel recipe I use. I ended up with this

Hi Quentin, Thank you very much for the review. Well, here, the two should go together. I admit my description is probably misleading. My initial "git checkout" was wrong (wrong path), so wasn't

Wiki: https://wiki.yoctoproject.org/wiki/Bug_Triage Attendees: Alexandre, Armin, Daiane, Michael, Randy, Richard, Ross, Saul, Stephen, Steve, Tim, Trevor ARs: -