All of lore.kernel.org
 help / color / mirror / Atom feed
From: Michael Opdenacker <michael.opdenacker@bootlin.com>
To: Peter Bergin <peter@berginkonsult.se>,
	yocto@lists.yoctoproject.org, Ross Burton <ross@burtonini.com>
Subject: Re: [yocto] Invalid checksums for SRC_URI ignored?
Date: Wed, 19 Jan 2022 14:59:50 +0100	[thread overview]
Message-ID: <c6038301-7fde-ba25-a75a-bc1c4f614271@bootlin.com> (raw)
In-Reply-To: <4cb625ab-23f3-f0e0-f8c4-b4feb65caddd@berginkonsult.se>

Peter, Ross

On 1/19/22 1:56 PM, Peter Bergin wrote:
> Hi,
>
> On 2022-01-19 13:16, Michael Opdenacker wrote:
>> Greetings,
>>
>> I reused a simple "hello" recipe and added a non-matching checksum to
>> it:
>>
>> ...
>> SRC_URI = "file://helloworld.c"
>> SRC_URI[md5sum] = "34f0efd76b4f18888888888833cdd129"
>> ...
>>
>> The rest of the recipe comes from
>> https://git.openembedded.org/openembedded-core/tree/meta-skeleton/recipes-skeleton/hello-single.
>>
>>
>> Why doesn't Bitbake stop, reporting that the checksum doesn't match the
>> source file?
>> Anyway, why does the recipe build without a checksum? Shouldn't
>> checksums be mandatory?
>
> No they are not mandatory for all fetchers. They are only used for
> content downloaded from non-local archives.
> https://docs.yoctoproject.org/bitbake/bitbake-user-manual/bitbake-user-manual-fetching.html#the-download-fetch
>
>
> https://github.com/openembedded/bitbake/blob/32180d5057c818a69987aada482e82acf3c72ef2/lib/bb/fetch2/__init__.py#L1268
>
>
> ^^ here you can see the selection of URI's that automatically needs a
> checksum.


Thanks for your replies. This all makes perfect sense then.
Thanks again
Michael.

-- 
Michael Opdenacker, Bootlin
Embedded Linux and Kernel engineering
https://bootlin.com



  reply	other threads:[~2022-01-19 13:59 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-01-19 12:16 Invalid checksums for SRC_URI ignored? Michael Opdenacker
2022-01-19 12:52 ` [yocto] " Ross Burton
2022-01-19 12:56 ` Peter Bergin
2022-01-19 13:59   ` Michael Opdenacker [this message]
2022-01-19 17:55     ` Richard Purdie

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=c6038301-7fde-ba25-a75a-bc1c4f614271@bootlin.com \
    --to=michael.opdenacker@bootlin.com \
    --cc=peter@berginkonsult.se \
    --cc=ross@burtonini.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.