None of that output looks like an error to me. Could you share some more context? E.g. the bitbake command you ran, the initial output showing the layers, versions and key config values, what expected

I saw that meta-kernel was used in the M3 build so I'm not going to drop recipes or rename the layer right now. I'll implement these changes after the Yocto 3.2 release.

It looks like your editor is not adding a final newline in some of these files. Most editors should have a setting to ensure a final newline is included in each file, if you can't find this you can al

Also, I think Mark's email address needs updating in the README as I got a bounce sending this reply. Mark, could you confirm?

It looks like you've removed an important comment there along with the old license header. I think there are a few other instances of this as well. Could you re-check this?

This sounds like a helpful contribution. To submit this please follow the guidelines in https://www.openembedded.org/wiki/How_to_submit_a_patch_to_OpenEmbedded. You should also check the README in the

#yocto

SRC_URI should start with "git://" to do a git clone. The "protocol" field can then be set to http, https or ssh if needed, I see you've already got that set to https after expansion so you should jus

#yocto

Hi folks, After a bit of a break I'm looking again at the meta-kernel layer and I've got some changes planned. I'd like to get some feedback on these from anyone who has looked at or used the meta-ker

What command did you run? What's your host distro, layers and branches/version, local.conf contents, etc? You need to give enough info for your issue to be understood. The email address is fine, just

Sorry to be blunt, but this email is meaningless. Please give some context and use a name other than "Yocto". You're not likely to get any helpful replies from an email like this.

I don't think any of us have crystal balls to predict the exact package versions we'll be using in October for the next release. We're close to the feature freeze point but high priority recipe update

<jester@...> wrote: Also worth noting: The exact versions used will depend on which commit from the dunfell branch you choose. You should follow updates to the stable branch to get the

#dunfell

<richard.purdie@...> wrote: If there was any comment about the layer naming I don't think it got to me. The only feedback I saw was that yocto-announce could not be used to announce re

Hey folks, I'd like to get the meta-kernel layer mirrored on git.yoctoproject.org so that we've got a backup available in case of any issues with GitLab. This has been requested by one of our users (h

Many thanks for taking these notes, I missed the call this week so good to be able to keep up to date :)

I know of https://github.com/jsbronder/meta-openrc but I've not tested it myself. Thanks,

Siddhartha, you're confusing the issue here by giving inaccurate advice. The original command posted by Pankaj was nearly correct: `sudo dd if=core-image-minimal-raspberrypi4.wic.bz2 of=/dev/sdb`. The

#linux #yocto

It's packaged on pypi: https://pypi.org/project/betatest/ I need to do a new release as I tidied a few things up and added a subtest wrapper after I published v0.1.0. This gives me a kick to get that

Another option could be to generate the output in the correct format directly from Python using something like this module which I wrote a few years back: https://gitlab.com/b5/BetaTest/betatest/-/blo

<severin.zwicker@...> wrote: Yes, it currently appears to be down. The relevant folks will be looking at it but it's still early in the US timezones.