The requirements file explicitly says cbor, and it turns out I can't read your message as I do have meta-arm present. I shall post cbor too tomorrow. Ross

This one is I think musl+mips 32Bit - considered that out of scope for initial fix. All erriors I checked so far share same: missing llvm-objdump - you do not have meta-clang in layers - I

<trevor.gamblin@...> wrote: Probably. Very curious how this worked as I don't have that layer locally! I'll double-check. Ross

On 2021-11-01 12:18, Ross Burton wrote: Did you mean python3-cbor2? The layer index suggests that python3-cbor is only in meta-iot-cloud/meta-arm/meta-ros-common.

fails during configure, I am using mips/musl locally but I guess it could be a common problem https://errors.yoctoproject.org/Errors/Details/615986/ on arm/glibc I see

Was my bad - did send a fix Andreas

I've seen this twice now, same recipe both times, so I assume it's something its doing which is upsetting pseudo. I suspect both times I swapped to/from systemd/init as INIT_MANAGER (w/o clearing

imgtool is part of MCUboot, used to sign images and manage keys. Signed-off-by: Ross Burton <ross.burton@...> --- .../recipes-devtools/python/python3-imgtool_1.8.0.bb | 12 ++++++++++++ 1 file

To avoid happening again: Have one line with REQUIRED_DISTRO_FEATURES only Signed-off-by: Andreas Müller <schnitzeltony@...> --- meta-gnome/recipes-gnome/gdm/gdm_41.0.bb | 4 +--- 1 file

--- .../jasper/{jasper_2.0.26.bb =3D> jasper_2.0.33.bb} | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) rename meta-oe/recipes-graphics/jasper/{jasper_2.0.26.bb =3D>

Signed-off-by: Michael Vetter <jubalh@...> --- .../jasper/{jasper_2.0.26.bb =3D> jasper_2.0.33.bb} | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) rename

seeing these when polkit is not in distro features, is there a way out ? ERROR: Nothing PROVIDES 'accountsservice'

Is there any possibility to merge this patch into dunfell? Currently, it is breaking an application that I'm working on, and I would like to know if there is any possibility for this patch to be

What you have is fine and here is why. Every major distribution is naming it gtk4, this is to accommodate API breaking changes and need to ship multiple versions of gtk, while dropping + is evident,

That also depends on whether gtk5 will be better at API compatibility, I just don't want to carry those awkward version suffixes forever. Python3 is annoying enough. Upstream dropping the '+' looks

<alex.kanavin@...> wrote: Did this to make the difference clear and to be prepared once they invent gtk5. What do others think? Andreas

This is release 1.41.0 (goat) of gRPC Core. For gRPC documentation, see grpc.io. Signed-off-by: Zheng Ruoqin <zhengrq.fnst@...> --- .../{python3-grpcio_1.41.0.bb =>

This is the first Cycler feature release in some years. New features include: Added Cycler.by_key, which produces values by key (#26) Added Cycler.__contains__, which adds support for in checks

Signed-off-by: Zheng Ruoqin <zhengrq.fnst@...> --- ...n3-grpcio-tools_1.41.0.bb => python3-grpcio-tools_1.41.1.bb} | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) rename