Wait, how is YAML more readable, if JSON is valid YAML? Alex

JSON is terrible for humans to read or edit, is this intended to be purely for the machine, or are humans meant to read it too? If humans are meant to work on the file I’d really prefer something

Hi, Alexandre: Thanks for the review, I did not quite follow you, you meant the 'type' argument being replaced wrongly? I dont see how. Could you share some details about your comment? //Ming Liu

I really don't like remove operations in OE-Core. If it is incompatible, why is it there in the first place? Does that need to be clang only? Cheers, Richard

Just realized that this went to the wrong mailing list, sorry. Please ignore.

Wrong mailing list, should go to oe-devel. Alex <adrian.freihofer@...> wrote:

Update to latest stable version: 1.30.8 * New request/response/indications: ** dms: new 'Foxconn FCC authentication v2' request/response. 1.30.6 * build: ** meson: fix 'export_packages' in GIR

Update modemmanager and libqmi to latest stable. Adrian Freihofer (2): libqmi: upgrade 1.30.4 -> 1.30.8 modemmanager: upgrade 1.18.8 -> 1.18.10 .../libqmi/{libqmi_1.30.4.bb => libqmi_1.30.8.bb}

Fixes build errors seen with clang error: the 'sse' unit is not supported with this instruction set Signed-off-by: Khem Raj <raj.khem@...> --- meta/recipes-extended/ltp/ltp_20220527.bb | 1 +

Fixes ERROR: QA Issue: : /work/x86_64-linux/libmodule-build-perl-native/0.4231-r0/sysroot-destdir/work/x86_64-linux/libmodule-build-perl-native/0.4231-r0/recipe-sysroot-native/usr/bin/config_data

As far as I know, qemuwrapper-cross should work in such case. You need to use qemuwrapper-cross instead of nativesdk-qemuwrapper-cross. Regards, Qi

Hi K, Add oe-core list and move poky to BCC to ensure follow to the main oe-core code review list. I've never done a build on btrfs let alone on a compressed btrfs volume. This does seem like it

Hi, Richard Thanks for your reply. OK, it seems that I didn't get the usage of nativesdk-qemuwrapper-cross every well. The problem I have is that when I created a rootfs(aarch64) under SDK

Sorry about those issues, v2 sent of both patches. Cheers, Richard

Resurrect sato-icon-theme and move to a version with scalable icons support to replace adwaita-icon-theme which no longer supports the icons we need for the sato desktop. Signed-off-by: Richard

To add back sato-icon-theme we need this small util. Signed-off-by: Richard Purdie <richard.purdie@...> --- meta/conf/distro/include/maintainers.inc | 1 +

Ya, for a 100% "standalone" tool, I'm not sure if we can do any real validation in python without external modules. For testing, can either add the requirement for the `python3-jsonschema` system

Since jsonschema is not a standard module, we need to think for a bit about how and when validation should occur with tools available directly in core. I would like it to happen every time json

Hello Richard, I believe you are missing HOMEPAGE here This warns: icon-naming-utils-0.8.90-r0 do_package_qa: QA Issue: Recipe LICENSE includes obsolete licenses GPLv2 [obsolete-license] Finally, I

Defining the format formally in a verifiable way is quite useful, thanks. I'll integrate it into my patchset. And yes, I have a different viewpoint: I do not want separate tools that need to be