Bitbake fetch does not re-fetch from network if gitrepo is found in DL_DIR

[christian.leeb@hitachienergy.com]

[-- Attachment #1: Type: text/plain, Size: 1148 bytes --]

Hi,

I did a bitbake virtual/kernel --runall=fetch, with a DL_DIR containing kernel git repo. This git repo does not contain the SRCREV 7818dfe57e requested.

Log suggests the fetch ran fine with the 7818dfe57e
recipe linux-ti-staging-rt-5.4.106+gitAUTOINC+7818dfe57e-r7a.spark10: task do_fetch: Succeeded

At this point I would have expected the fetch found the repo in DL_DIR but the requested commit is t's not up-to-date hence it would reach out to the network.

Later I call bitbake again to build the kernel and I'm getting this error.

ERROR: linux-ti-staging-rt-5.4.106+gitAUTOINC+7818dfe57e-r7a.spark10 do_unpack: Bitbake Fetcher Error: UnpackError('No up to date source found: clone directory not available or not up to date: /home/vsts-agent/azagents/build-1/_work/_temp/localdl//git2/dev.azure.com.PG-CT.PGLinux._git.pg-linux; shallow clone not enabled', 'git://dev.azure.com/PG-CT/PGLinux/_git/pg-linux;protocol=https;branch=pg-am57xx-ti-rt-linux-5.4.106')

This suggests that fetch was happy finding the repo in DL_DIR but did not care that the requested commit was missing.
Is this the intended behavior?

BR, Chris

[-- Attachment #2: Type: text/html, Size: 3159 bytes --]