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: Fri, 05 Dec 2025 08:20:34 -0800 [thread overview]
Message-ID: <123016.1764951634952562755@lists.yoctoproject.org> (raw)
In-Reply-To: <33793480-bdcc-4b88-ab11-0d493118836e@gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1005 bytes --]
Thanks a lot, Gyorgy, for your feedback. Maybe a bit of background what we are trying to do.
We have the following situation - we call it "top-up":
We start bitbake fetch as described with DL_DIR containing the sources of a previous release.
The state cache is empty.
The idea is that bitbake fetch only re-fetches repos which are not up-to-date.
In a regular release, we always fetch all sources anew from upstream (debatable if this is the right approach). At the end of the release we archive all sources of the dl folder. We do not archive the sstate cache.
For reproducing a release we take the archive of the release and rebuild without network (BB_NONETWORK)
The motivation for "top-up" came from last week's outage of cloudflare: we urgently needed to issue a release, but one upstream server was down. So we used dl archive of previous release, removed the "BB_NONETWORK and hoped it would fetch the missing stuff (in my example some commits of the kernel) and then we can build.
[-- Attachment #2: Type: text/html, Size: 1141 bytes --]
next prev parent reply other threads:[~2025-12-05 16:20 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 [this message]
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=123016.1764951634952562755@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.