You can and should use PREMIRROR like with any other source fetched by bitbake fetcher. Use BB_GENERATE_MIRROR_TARBALLS, then rsync your downloads directory (exclude .done, bad-checksum files and git2

I agree that there are other more important things, but I also like style (only in code - human looks are overrated :)). If the tool is executed locally before sending the contribution (and Carsten do

use SRCPV in PV as the error says

#bitbake

Hi Armin, can you please merge this to master branch? It's in master-next for a while, but not in master and master-next is missing some changes from master as well, openscap upgrade and kas changes l

Yes, it's expected. native recipes shouldn't be MACHINE specific, so shouldn't use MACHINEOVERRIDES, see: meta/classes-recipe/native.bbclass:MACHINEOVERRIDES = "" meta/classes-recipe/nativesdk.bbclass

#yocto

Trevor already won this race (I was second, you're third) :) https://patchwork.yoctoproject.org/project/yocto/list/?series=&submitter=&state=&q=mickledore&archive=&delegate=

* oe-core switched to mickedore in: https://git.openembedded.org/openembedded-core/commit/?id=57239d66b933c4313cf331d35d13ec2d0661c38f Signed-off-by: Martin Jansa <Martin.Jansa@...> --- conf/lay

* oe-core switched to mickedore in: https://git.openembedded.org/openembedded-core/commit/?id=57239d66b933c4313cf331d35d13ec2d0661c38f Signed-off-by: Martin Jansa <Martin.Jansa@...> --- conf/lay

Hi Ferry, don't get discouraged from working on jobserver related issues by some remarks. Yes your HW configuration is a bit extreme, but similar issues are easily reproducible on beefier HW as well (

Hi, that is intentional, recipes should fetch sources with bitbake fetcher (which respects MIRROR/PREMIRROR/DL_DIR etc) in do_fetch and network shouldn't be used in other tasks (unless explicitly enab

And here is another example why nobody should be using meta-socketcan: https://github.com/ZoranStojsavljevic/meta-socketcan/commit/cefd86cd1def9ad2e63be527f8ce36a076d7e17c# You cannot change the decla

https://bugzilla.yoctoproject.org/show_bug.cgi?id=13904 is one of the bugs I think.

Agreed with Rudolf. If the layer maintainer didn't bother to do at least do one build with new release and adjust LAYERSERIES_COMPAT, then I don't consider that layer well maintained (it could be some

You can also chown the files after unpacking them (like in https://github.com/webOS-ports/meta-webos-ports/commit/9fd17a67cdbed92df13a14b002a189b4c6c2d442)

* the next release 4.2 will be named mickledore Signed-off-by: Martin Jansa <Martin.Jansa@...> --- conf/layer.conf | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/conf/layer.co

There was another thread about sending e-mails with git send-email this week: https://lists.openembedded.org/g/openembedded-core/message/171101 +Robert which pointed to this longer explanation: https:

> PARALLEL_MAKE = "-j ${@int(oe.utils.cpu_count() / 4)}" This won't be optimal in cases where you're rebuilding just one recipe in incremental build which will be finished much faster if you can unlea

Hello, the fetch is still executed in do_fetch task (and uses MIRROR/PREMIRROR etc), maybe you mean the 2nd fetch when the tag doesn't exist in specified branch added here: https://github.com/openwebo

In webOS we use do_unpack postinst which checks that the SRCREV matches with the expected tag name and that the tag is annotated, see https://github.com/webosose/meta-webosose/blob/master/meta-webos/c

You can use VIRTUAL-RUNTIME_sed variable instead of 'sed' _everywhere_ and then change the preferred runtime provider in your DISTRO config. Similar case for "stat" from busybox in webOS OSE: https://