Hey, I'm just updating my calendar for the new year and spotted a bit of confusion. The website page https://www.yoctoproject.org/public-virtual-meetings/ shows the meeting times an hour earlier than

Cc'ing the maintainers listed in the readme along with Changqing Li as discussed during the Yocto Project call on Tuesday. Could you confirm who's maintaining patchtest these days and update the readm

Cc'ing the maintainers listed in the readme along with Changqing Li as discussed during the Yocto Project call on Tuesday. Could you confirm who's maintaining patchtest-oe these days and update the re

Ah ok. I have a pet hate of layers with a master branch that doesn't actually work with master of oe-core and other layers. I'd rather see a repository with no master branch! In this case we're buildi

Looking at the link you gave [1], you probably need to use "--with-nghttp2=<PATH>" and add nghttp2 to DEPENDS. You may need to find or write a recipe for that library. [1]: https://serversforhackers.c

#yocto #raspberrypi

Thanks for that, it may have got broken in the layer index when we moved the repo from our private Bitbucket instance over to GitHub. I've resubmitted now.

Hi, I'd like to make sure meta-sancloud (https://github.com/SanCloudLtd/meta-sancloud) is listed in the layer index. I can't see it listed for either of the branches we support (thud & rocko). However

Are you using an existing image recipe or writing your own? If it's your own, do you have packagegroup-core-boot included? Thanks,

Ping on this and the following patch.

Ping.

You may be better asking this on the u-boot list <u-boot@...>.

Following up on the email below, I've created a "community" subgroup to the OpenEmbedded group on GitLab: https://gitlab.com/openembedded/community. This should help to avoid any confusion with the re

When running patchtest locally to figure out what was wrong with my patch, I saw the similar exceptions for each test module: Traceback (most recent call last): File "/usr/lib/python3.6/unittest/case.

The addError() handler is called outside of an actual exception handler so sys.exc_info() doesn't actually return an exception. This means that traceback.print_exc() doesn't know what to print. Instea

The case sensitivity of the checks for the "Upstream-Status" label should match so that failure messages make sense. The checks in the parse_upstream_status module are case sensitive and so the initia

If you want to make changes like this in a distro or local configuration, I think it'd be easier to add a new .wks file and override WKS_FILE. FYI, for meta-raspberrypi we usually take patches through

These settings feel distro-specific to me. They're not required for how many of us use the Raspberry Pi so it's best not to force them on everyone. Thanks,

This is something I covered in the Yocto Project Summit in Lyon at the end of October. I'm hoping to get the project documentation updated to reflect what was discussed but that will take a little tim

You could start by looking at how meta-freertos (https://github.com/aehs29/meta-freertos) achieves this. It has support for running the resulting bare-metal app under qemu which you might not need, bu

Hey folks, We had some initial discussion at OEDEM about the patch submission process and how repositories are hosted (see https://docs.google.com/document/d/1Qm1mJ6xLozWW9NgBnokue7TmhwgFP8b2HR8TUlaQw