"C. Andy Martin" <cam@...> wrote: Yeah. Come to think of it, directory mismatches are already probably blowing up differently because we're more concerned about that. Probably okay. -s

I agree this is not the ideal solution. However, I was basing this compromise on this commit: commit 691a2304c8c29a3b7d5977908ef82aaf188f5ba0 Author: Seebs <seebs@...> Date: Fri Apr 13

All, The triage team is starting to try and collect up and classify bugs which a newcomer to the project would be able to work on in a way which means people can find them. They're being listed on

I see git describe hung during bitbake parse stage in few of meta-oe recipe and also kernel recipe with this patch. <richard.purdie@...> wrote:

<alex.kanavin@...> wrote: right, this might be good to have as comment on top of that assignment for future reference

On Mon, Apr 25, 2022 at 9:19 AM Carlos Rafael Giani via lists.openembedded.org <crg7475=mailbox.org@...> wrote: fair enough.

According to https://gstreamer.freedesktop.org/releases/1.20/ , libsoup 3 support isn't stable: > Runtime compatibility support for libsoup2 and libsoup3 (libsoup3

Rust is self-hosting and bootstraps itself with a pre-built previous version of itself. Just like gcc. The exact (previous) version that has been used is specified in the source tarball, here we

"C. Andy Martin" <cam@...> wrote: I'm distrustful of this because I feel like, in the case where we have apparently-stale information in the database, we really should be coming back with

We have soup3 as well. I wonder if that should also be an option ?

Hi, As already tracked at [1], building an arm32 fails with a OE sdk. This is caused by the fact that it is a Canadian build (or at least looks like it). In my case: "--build=x86_64-linux

why 1.59.0 ? its a bit counter-intuitive.

Hi Steve, Sure, will send it for meta-openembedded. Thanks, Best Regards, Ranjitsinh Rathod Technical Leader | | KPIT Technologies Ltd. Cellphone: +91-84606

On Mon, Apr 25, 2022 at 3:57 AM Steve Sakoman via lists.openembedded.org <steve=sakoman.com@...> wrote: Heh, now I know why I "forgot" to take this patch in dunfell -- there is no

This clears up some confusing packageconfigs. Signed-off-by: Carlos Rafael Giani <crg7475@...> --- .../gstreamer/gstreamer1.0-plugins-bad_1.20.1.bb | 2 ++

Signed-off-by: Carlos Rafael Giani <crg7475@...> --- .../gstreamer/gstreamer1.0-plugins-good_1.20.1.bb | 7 ++++++- 1 file changed, 6 insertions(+), 1 deletion(-) diff --git

For hard-links there are many potential races where the path may not yet exist in the database but we find an inode match on the linked file. For instance, if one sub-process performs the link and

The previous minimially invasive git intercept simply isn't enough. For example, meson used in the igt-gpu-tools recipe hardcodes the path to git in the configure step so at install time, changing

<ranjitsinhrathod1991@...> wrote: Yes, of course! Thanks for the reminder. Steve

https://git.yoctoproject.org/poky/commit/?id=21559199516a31c7635c5f2d874eaa4a92fff0e5 However this isn't quite enough as some things encode the path to git into build files so the PATH change at