We found the source of the uninative fetch problem:
toggle quoted messageShow quoted text
SOURCE_MIRROR_URL needs to be set in order for uninative to be picked up from local mirror.
The standard PREMIRRORS mechanism doesn't work for this single tarball.
So every time a clean poky build took place it always went to the internet to fetch the uninative tarball
the first time and store it in the local build download.
I think this should be clearly documented somewhere in the yocto manual?
On 2020-08-05 10:07 a.m., Scott Branden wrote:
On 2020-08-05 2:50 a.m., Richard Purdie wrote:
On Tue, 2020-08-04 at 14:36 -0700, Scott Branden viaYes, the uninative tarball *is* cached but I see repeated downloads.
With downloads.yoctoproject.org down again this begs the question:Those are good questions.
Why does uninative tarball get fetched by default from the internet
Why is it in not cached like every other tarball that is downloaded
The default behaviour for the yocto project should be to have the
tarball stored in the yocto cache such that it is not fetched every
As far as I know on my own local builds, the uninative tarball *is*
cached locally in DL_DIR. We don't see repeated downloads on the
autobuilder either so it appears to work there too.
If you're not seeing that it would definitely be something toI just did a clone of poky.git and the repeated downloads do NOT happen.
So I now need to investigate what is different when adding layers and conf settings
that is causing the issue.
Cheers,Thanks for confirming the uninative caching should work, but it is not in my environment and I will have to investigate.