public inbox for yocto@lists.yoctoproject.org
 help / color / mirror / Atom feed
From: Gyorgy Sarvari <skandigraun@gmail.com>
To: yocto@lists.yoctoproject.org, christian.leeb@hitachienergy.com
Subject: Re: [yocto] Bitbake fetch does not re-fetch from network if gitrepo is found in DL_DIR
Date: Thu, 4 Dec 2025 20:23:14 +0100	[thread overview]
Message-ID: <6a0d63c8-3a01-44a3-bc52-27ce3f5587dc@gmail.com> (raw)
In-Reply-To: <MUyE.1764856618420625622.Sp84@lists.yoctoproject.org>

On 12/4/25 14:56, christian.leeb via lists.yoctoproject.org wrote:
> 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?
>

Generally speaking this does not sound intentional - Bitbake has checks
for this, it verifies during do_fetch explicitly if the requested
revision is already present in the local clone, or it needs to be updated.

Which version of Bitbake/Yocto are you using? Also, how do you specify
the revision in the recipe? (revision, tagname in SRCREV, something else?) 
A minimal reproduction could be also useful, if available.

> BR, Chris
>
>
> -=-=-=-=-=-=-=-=-=-=-=-
> Links: You receive all messages sent to this group.
> View/Reply Online (#66088): https://lists.yoctoproject.org/g/yocto/message/66088
> Mute This Topic: https://lists.yoctoproject.org/mt/116612004/6084445
> Group Owner: yocto+owner@lists.yoctoproject.org
> Unsubscribe: https://lists.yoctoproject.org/g/yocto/unsub [skandigraun@gmail.com]
> -=-=-=-=-=-=-=-=-=-=-=-
>



  reply	other threads:[~2025-12-04 19:23 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 ` Gyorgy Sarvari [this message]
2025-12-04 21:41   ` [yocto] " 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
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=6a0d63c8-3a01-44a3-bc52-27ce3f5587dc@gmail.com \
    --to=skandigraun@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox