From: christian.leeb@hitachienergy.com
To: "Gyorgy Sarvari" <skandigraun@gmail.com>, yocto@lists.yoctoproject.org
Subject: Re: [yocto] Bitbake fetch does not re-fetch from network if gitrepo is found in DL_DIR
Date: Thu, 04 Dec 2025 13:41:45 -0800 [thread overview]
Message-ID: <96936.1764884505239996619@lists.yoctoproject.org> (raw)
In-Reply-To: <6a0d63c8-3a01-44a3-bc52-27ce3f5587dc@gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1796 bytes --]
I'm using Yocto 4.0, kirkstone.
We set
URI is git://dev.azure.com/PG-CT/PGLinux/_git/pg-linux;protocol=https;branch=pg-am57xx-ti-rt-linux-5.4.106
SRCREV="7818dfe57e1d1e2d2eaf039d1231560611811d67"
BRANCH="pg-am57xx-ti-rt-linux-5.4.106"
The DL_DIR contains above repo (git2/dev.azure.com.PG-CT.PGLinux._git.pg-linux) and above branch but just not the latest commit of this branch.
Also, between
recipe linux-ti-staging-rt-5.4.106+gitAUTOINC+7818dfe57e-r7a.spark10: task do_fetch: Started
and
recipe linux-ti-staging-rt-5.4.106+gitAUTOINC+7818dfe57e-r7a.spark10: task do_fetch: Succeeded
there is only a few seconds. Another proof IMHO that there was no network access.
Fetch works properly if the repo is not present at all in the DL_DIR.
I also check if shallow clone is set: seems that this is not the case unless there is some other setting to consider.
bitbake virtual/kernel -e | grep ^BB_GIT_SHALLOW
BB_GIT_SHALLOW:pn-binutils="1"
BB_GIT_SHALLOW:pn-binutils-cross-arm="1"
BB_GIT_SHALLOW:pn-binutils-cross-canadian-arm="1"
BB_GIT_SHALLOW:pn-binutils-cross-testsuite="1"
BB_GIT_SHALLOW:pn-binutils-crosssdk-x86_64-spark-linux="1"
BB_GIT_SHALLOW:pn-binutils-native="1"
BB_GIT_SHALLOW:pn-glibc="1"
In addition I got this info from the internet:
Why do_fetch didn’t update the repo:
BitBake’s fetcher logic:
If the repo exists in DL_DIR and the SRCREV is marked as available (based on metadata), it skips network fetch.
It doesn’t *verify the actual commit presence during do_fetch* —that check happens in do_unpack.
So the 2-second fetch means it reused the cached repo without pulling new commits.
I wonder what it means " SRCREV is marked as available (based on metadata) ". It's obviously not there.
Thanks a lot for your support.
Chris
[-- Attachment #2: Type: text/html, Size: 7914 bytes --]
next prev parent reply other threads:[~2025-12-04 21:41 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-12-04 13:56 Bitbake fetch does not re-fetch from network if gitrepo is found in DL_DIR christian.leeb
2025-12-04 19:23 ` [yocto] " Gyorgy Sarvari
2025-12-04 21:41 ` christian.leeb [this message]
2025-12-05 15:46 ` Gyorgy Sarvari
2025-12-05 16:20 ` christian.leeb
2025-12-05 17:21 ` Alexander Kanavin
2025-12-05 17:24 ` Alexander Kanavin
2025-12-05 18:12 ` Gyorgy Sarvari
2025-12-08 10:31 ` Alexander Kanavin
2025-12-08 16:45 ` Gyorgy Sarvari
2025-12-09 8:01 ` christian.leeb
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=96936.1764884505239996619@lists.yoctoproject.org \
--to=christian.leeb@hitachienergy.com \
--cc=skandigraun@gmail.com \
--cc=yocto@lists.yoctoproject.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.