From: Gyorgy Sarvari <skandigraun@gmail.com>
To: Alexander Kanavin <alex.kanavin@gmail.com>, yocto@lists.yoctoproject.org
Cc: christian.leeb@hitachienergy.com
Subject: Re: [yocto] Bitbake fetch does not re-fetch from network if gitrepo is found in DL_DIR
Date: Fri, 5 Dec 2025 19:12:03 +0100 [thread overview]
Message-ID: <96c47e76-9e94-4d53-90a1-57488b165612@gmail.com> (raw)
In-Reply-To: <CANNYZj8A46=oc3sD=F2H=A33rjmue=tVhTtVBJTabfO3EJLuDQ@mail.gmail.com>
On 12/5/25 18:24, Alexander Kanavin wrote:
> On Fri, 5 Dec 2025 at 16:46, Gyorgy Sarvari via lists.yoctoproject.org
> <skandigraun=gmail.com@lists.yoctoproject.org> wrote:
>> I have been thinking about this, and also tried to reproduce it,
>> unsuccessfully...
>>
>> If fetch is deemed successful, it is stored in the shared state cache,
>> and then it is not repeated until the relevant signature changes - I
>> think this is the metadata reference you found.
>> However as long as the download folder's content is only modified by one
>> project only, it supposed keep track of it fine.
>>
>> One question about the DL_DIR: is it possible that it is shared between
>> multiple projects, while keeping separate shared state cache? Or that
>> the DL_DIR's content modified manually?
>> The shared state cache supposed to keep track of what is downloaded by
>> bitbake and what is not, but if the DL_DIR's content is changed without
>> bitbake (or by a separate bitbake), that can break the shared state, and
>> cause such issues.
> This is not correct. Shared state does not track what is downloaded.
It depends on how you interpret it. Sstate does track the do_fetch task,
and does know if it needs to re-executed or not.
> It is also fine to share DL_DIR between multiple builds and projects.
I did not write that it is not fine to share DL_DIR, but but you need to
know some caveats. If you run bitbake -c cleanall in one project, you
are up for a good time in the other one, if they use the same recipe.
>
> Alex
next prev parent reply other threads:[~2025-12-05 18:12 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
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 [this message]
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=96c47e76-9e94-4d53-90a1-57488b165612@gmail.com \
--to=skandigraun@gmail.com \
--cc=alex.kanavin@gmail.com \
--cc=christian.leeb@hitachienergy.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.