Scott is aware and on top of it. js Richard Purdie <richard.purdie@...> schrieb am Fr., 4. Feb. 2022, 18:51:

I did already talk with Scott Murray and there are patches ready for this. I think meta-aws was ok? Cheers, Richard

Hi Richard, Reaching out due to a failure in meta-agl-core on the Autobuilder. Weston has been updated to 10.x, but the bbappend in meta-agl-core is still 9.x based. Do you have plans for

I am on SWAT and will start reviewing the logs in my morning. Sau! -- Sau!

This makes a lot of sense to me and it's clear now. It didn't come across this way in prior responses. Thank you for taking the time to put this together. We can't remove aws-c-common from the

It may be a deliberate choice but I suspect there are some issues you aren't considering, specifically: a) it breaks anyone doing offline builds b) it means source archives don't function correct c)

So the main error is: aws-c-auth-0.6.1-r0 do_packagedata_setscene: ExpansionError('SRCPV', '${@bb.fetch2.get_srcrev(d)}', FetchError('The SRCREV_FORMAT variable must be set when multiple SCMs are

The main drawback is that then you are not able to build with BB_NO_NETWORK = 1 and so there is no way to ensure you have locally all the code you need to reproduce the build in case Amazon gets out

The choice to use tags is a deliberate one. For all AWS repos that meta-aws builds recipes we use release tagging to align with a specific release. While tags can move (aka the old school CVS

Ouch, no SRCREVs? I'm guessing we need to extend yocto-check-layer with another test? :) -- Denys

wrote: I did just have a look at the aws-c-iot

Ah, interesting. Will you be tracking that on your side or should I open a bug on bugzilla.yp.org? -- Alexandre Belloni, co-owner and COO, Bootlin Embedded Linux and Kernel

This was: meta meta-poky meta-yocto-bsp = "master:9f8e74668730e6eb3eb44df187a40d0a0f8c7b0a" meta-oe meta-python meta-networking = "master:a558d51fecda3e66ace21d02b57ab61bf122fdc1" meta-aws

Hi Alexandre, I'm adding Nathan to see if there's anything he can see. I am not familiar with the warning at all, it looks new to me. Which build step has the commit hash for the repos we're checking

Hello, It's been a few days that I'm struggling to understand what happened in this build. I've been looking at the fetcher changes, meta-aws changes but couldn't find anything

Hello everyone, Following the winter break, I would like to organize SWAT duty rotation. I've again prepared a schedule so it is easier for each one of you to plan for SWAT duty. Please check the

Sure, it was kind of hidden in all those meta-oe warnings so I wanted to make sure you knew about it. -- Alexandre Belloni, co-owner and COO, Bootlin Embedded Linux and Kernel

Thank you - it is in our current sprint to fix, it was noted last week when the distutils warnings across openembedded really alarmed us. It’s a simple fix so I don’t expect an extended CR :D

Hello Richard, There is a new warning in meta-aws: WARNING:

Good morning Alexandre, Sorry, I forgot about this work I am starting my work today Where I can check rotation shedule in feature? Also I will do this work first time, Oleksiy(oobitots@...) from my