From: Enrico Scholz <enrico.scholz@sigma-chemnitz.de>
To: Richard Purdie <richard.purdie@linuxfoundation.org>
Cc: Frederic Martinsons <frederic.martinsons@gmail.com>,
bitbake-devel@lists.openembedded.org
Subject: ';sha256sum=' attribute in SRC_URI (was: [bitbake-devel] [PATCH] fetch:crate: create versioned 'name' entries)
Date: Thu, 06 Apr 2023 16:18:30 +0200 [thread overview]
Message-ID: <lyfs9daybt.fsf_-_@ensc-pc.intern.sigma-chemnitz.de> (raw)
In-Reply-To: <ab8238c55687c8db85f9325a13f31b95c228c33c.camel@linuxfoundation.org> (Richard Purdie's message of "Thu, 06 Apr 2023 13:14:21 +0100")
Richard Purdie <richard.purdie@linuxfoundation.org> writes:
> Now I've been looking more closely at this, I did start to wonder if we
> shouldn't just put ;sha256sum=XXX parameters onto the crate urls we
> generate though? If we do that, we don't need to name them at all.
I just tested this with
SRC_URI += " \
crate://crates.io/addr2line/0.19.0;sha256sum=a76fd60b23679b7d19bd066031410fb7e458ccc5e958eb5c325888ce4baedc97 \
crate://crates.io/adler/1.0.2;adler-1.0.2.sha256sum=f26201604c87b1e01bd3d98f8d5d9a8fcbb815e8cedb41ffccbeb4bf593a35fe \
"
and got
| do_fetch: Missing SRC_URI checksum, please add those to the recipe:
| SRC_URI[addr2line-0.19.0.sha256sum] = "a76fd60b23679b7d19bd066031410fb7e458ccc5e958eb5c325888ce4baedc97"
It seems that ';sha256sum' does not suffice but that you have to dup the
'name'.
Enrico
next prev parent reply other threads:[~2023-04-06 14:18 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-04-05 10:16 [PATCH] fetch:crate: create versioned 'name' entries Enrico Scholz
2023-04-05 12:03 ` [bitbake-devel] " Frédéric Martinsons
2023-04-05 12:09 ` Enrico Scholz
2023-04-05 12:21 ` Frédéric Martinsons
2023-04-05 12:24 ` Enrico Scholz
2023-04-05 12:50 ` Frédéric Martinsons
[not found] ` <17530ADB1695B5D1.3977@lists.openembedded.org>
2023-04-05 16:28 ` Frédéric Martinsons
2023-04-05 16:44 ` Enrico Scholz
2023-04-05 17:05 ` Frédéric Martinsons
2023-04-06 8:45 ` Richard Purdie
2023-04-06 10:05 ` Frédéric Martinsons
2023-04-06 10:15 ` Richard Purdie
2023-04-06 10:20 ` Enrico Scholz
2023-04-06 12:14 ` Richard Purdie
2023-04-06 13:00 ` Frédéric Martinsons
2023-04-06 13:44 ` Richard Purdie
2023-04-06 13:57 ` Frédéric Martinsons
2023-04-06 14:01 ` Enrico Scholz
2023-04-06 14:18 ` Enrico Scholz [this message]
2023-04-06 14:46 ` ';sha256sum=' attribute in SRC_URI (was: [bitbake-devel] [PATCH] fetch:crate: create versioned 'name' entries) Frédéric Martinsons
2023-04-05 12:21 ` [PATCH, v2] fetch2/crate: create versioned 'name' entries Enrico Scholz
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=lyfs9daybt.fsf_-_@ensc-pc.intern.sigma-chemnitz.de \
--to=enrico.scholz@sigma-chemnitz.de \
--cc=bitbake-devel@lists.openembedded.org \
--cc=frederic.martinsons@gmail.com \
--cc=richard.purdie@linuxfoundation.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.