> Note went and modified ./meta/recipes-core/ovmf/ovmf_git.bb to use "http"... That is clearly wrong, you shouldn't change the git:// at the beginning of SRC_URI, just the ";protocol=git" to ";protoco

#yocto

your 2nd meta-intel probably still has: LICENSE_PATH += "${LAYERDIR}/custom-licenses" in layer.conf without having this directory included in the layer?

#yocto

This URL also fetches for me without any issues. If you cannot reach it from your location, you can still put an archive with it to your premirror or redirect it to some other repo accessible to you w

#yocto

There were only a few changes needed between dunfell and gatesgarth to keep it building and I feel guilty for sending half of them - and pinging you on FB :). I don't have interest in python2, but it'

Small typo in commit summary, but other than that please merge :).

I was able to reproduce this in one of my build setups and confirm that backporting this commit helps (and haven't found any other issues while building our images). I've sent the backport request now

For uninative you can just use latest dunfell with https://git.openembedded.org/openembedded-core/commit/?h=dunfell&id=0f01fb2286335dd0da0c7be3f56c36a0fced3e42 For dpkg you can just try latest, but I'

Are you trying to use it with openssl-1.0.*? Either use openssl-1.1 or revert the changes from https://github.com/apenwarr/wvstreams/pull/2/commits.

Are you sure this is the whole SRC_URI and that there aren't some other parts added through some .bbappend? Always use "bitbake -e" to see whatever bitbake sees when building the recipe to make sure.

Add "common" git repo to SRC_URI and set SRCREV + SRCREV_FORMAT for it, instead of using git submodules to fetch it.

You can backport https://git.openembedded.org/openembedded-core/commit/?h=dunfell&id=2cca75155baec8358939e2aae822e256bed4cfe0

#linux #qemu #yocto

/opt/yocto_downloads or /opt/downloads?

#yocto

This 0001-mtd-utils-Fix-return-value-of-ubiformat.patch patch was recently backported to dunfell in https://git.openembedded.org/openembedded-core/commit/?h=dunfell&id=3ee98b6c9ddd1dd0825245ca672236b7

Hi, having both would be useful, but you have to ask upstream iso-codes developers why they also removed master, OE DL_DIR just followed what they did in upstream, which unfortunately includes pruning

Hi, it's know issue already fixed in master, see https://lists.openembedded.org/g/openembedded-architecture/message/1108 thud is pretty much out of support and probably won't be fixed there, you shoul

There is no limitation like that, but it's quite easy to break that, you mentioned some ugly BSP before, I wouldn't be surprised if it's broken there. What worked well for me over the years is using t

Yes, it's worth. Thanks

Yes, in local.conf or distro config, both work fine. Maybe your PNBLACKLIST you're trying to unblacklist is using normal assignment instead of weak one? See http://git.openembedded.org/meta-openembedd

I don't use WR, but setting it to empty works fine for me. Why do you think it shouldn't work? See https://git.openembedded.org/openembedded-core/tree/meta/classes/blacklist.bbclass#n18

You can add a layer which will set LAYERSERIES_COMPAT for another layer, but it needs to be parsed before the layer you want to change, e.g.: https://github.com/webosose/meta-webosose/blob/thud/meta-q