Indeed, that would be concerning for us as well. Would it be possible to ignore PREMIRRORS based on the recipe layer? Alternatively, we could create blocklists for heavy packages that need to fetch fr

This would be a helpful addition for us when upgrading between named Yocto releases. Normally, when we are ready to upgrade, we checkout the HEAD for the named branch and try to get everything working

I mentioned that we remove that directory, and it does indeed solve a lot of problems. Not sure that it was clear from the original message, but whenever we get a random error on the first build after

Hello all. My organization has been working with Yocto recently, and we have noticed that there are often weird errors encountered after updating revisions within a release branch (e.g., 3.1.3 -> 3.1.