public inbox for bitbake-devel@lists.openembedded.org
 help / color / mirror / Atom feed
From: pedro.ms.ferreira@ctw.bmwgroup.com
To: bitbake-devel@lists.openembedded.org
Subject: Re: [PATCH] fetch2: avoid reuse download filenames
Date: Mon, 02 Mar 2026 08:54:15 -0800	[thread overview]
Message-ID: <1127752.1772470455842490403@lists.openembedded.org> (raw)
In-Reply-To: <e58fedf42052698a50007bd5d49a70e0b77aa702.camel@linuxfoundation.org>

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

Hi Richard,

This was detected internally when users modify source files and update
the hashes inside the recipes to match. Bitbake is allowing this operations
because it identifies a mismatch and renames it to procede with the download.

I tested this locally with:

- Create a source file, for example, test_download.tar.gz
- Create a simple http server (python3 -m http.server 1212 )
- Create a small recipe, local_test.bb
------------------------------------------------------------------------
SUMMARY = "local test recipe"
DESCRIPTION = "Downloads and installs test files"
LICENSE = "CLOSED"

SRC_URI = "http://0.0.0.0:1212/test_download.tar.gz"

S = "${WORKDIR}"

SRC_URI[md5sum] = "12e597833772126eade44740570aab3c"
SRC_URI[sha256sum] = "f03e325aa451beda1b340a7ce0fcfd620b74c86e12b8156a3d4949f7de67fc87"

do_install() {
install -d ${D}/etc/test
install  ${S}/README.md -C ${D}/etc/test
}

FILES:${PN} = "/etc/test/README.md"

------------------------------------------------------------------------
- Run it: bitbake -C fetch local-test
- Modify source file
- Update the hash
- Run it: bitbake -C fetch local-test
- A warning is raised: WARNING: local-test-1.0-r0 do_fetch: Renaming /home/test/yocto-downloads/test_download.tar.gz to /home/test/yocto-downloads/test_download.tar.gz_bad-checksum_f03e325aa451beda1b340a7ce0fcfd620b74c86e12b8156a3d4949f7de67fc87
- Bitbake continues the next steps with this new tarball.

Cheers.

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

  reply	other threads:[~2026-03-02 16:54 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-03-02 15:14 [PATCH] fetch2: avoid reuse download filenames Pedro Ferreira
2026-03-02 15:56 ` [bitbake-devel] " Richard Purdie
2026-03-02 16:54   ` pedro.ms.ferreira [this message]
2026-03-02 17:17     ` Yoann Congal
2026-03-05 10:22   ` pedro.ms.ferreira
2026-03-05  7:39 ` [bitbake-devel] " Mathieu Dubois-Briand
2026-03-05 15:21   ` pedro.ms.ferreira

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=1127752.1772470455842490403@lists.openembedded.org \
    --to=pedro.ms.ferreira@ctw.bmwgroup.com \
    --cc=bitbake-devel@lists.openembedded.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