From: Javier Viguera <javier.viguera@digi.com>
To: <openembedded-devel@lists.openembedded.org>
Subject: Re: checksums for multiple sources
Date: Wed, 9 Apr 2014 11:00:25 +0200 [thread overview]
Message-ID: <53450C29.5060202@digi.com> (raw)
In-Reply-To: <53450A23.3060107@linaro.org>
Hi Trevor,
You can put names to the different tarballs and then set the checksums
for each one of them with following syntax:
SRC_URI = " \
http://...;name=tarball1 \
http://...;name=tarball2 \
"
SRC_URI[tarball1.md5sum] = "..."
SRC_URI[tarball1.sha256sum] = "..."
SRC_URI[tarball2.md5sum] = "..."
SRC_URI[tarball2.sha256sum] = "..."
-
Javier Viguera
Software Engineer
Digi International® Spain S.A.U.
On 09/04/14 10:51, Trevor Woerner wrote:
> Is there any way to specify for which source tarball a particular
> checksum is referring?
>
> meta-openembedded/meta-oe/recipes-extended/acpica/acpitests_20140114.bb
> has 2 source tarballs (and a patch):
>
> SRC_URI =
> "https://acpica.org/sites/acpica/files/acpitests-unix-${PV}.tar.gz \
>
> https://acpica.org/sites/acpica/files/acpica-unix2-${PV}.tar.gz \
> file://0001-Fixup-aapits-build.patch \
> "
>
> but only one set of checksums:
>
> SRC_URI[md5sum] = "c72b61e092d2b25726dfff6e455116c9"
> SRC_URI[sha256sum] =
> "368f69296edef5138fd33affa2d50bdcdd1dfd2f6919ba782f8ecf03971a3a2c"
>
>
> My build fails because it tries to verify the one checksum against both
> source tarballs, which fails:
>
> File: '/home/trevor/devel/Downloads/acpica-unix2-20140114.tar.gz'
> has md5 checksum fcd4b7304f1bfabc7d4b9cfdecc6b0c6 when
> c72b61e092d2b25726dfff6e455116c9 was expected
>
> NOTE: this checksum is correct for the first tarball
> (acpitests-unix-${PV}.tar.gz), but not the second
> (acpica-unix2-${PV}.tar.gz).
>
next prev parent reply other threads:[~2014-04-09 9:01 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-04-09 8:51 checksums for multiple sources Trevor Woerner
2014-04-09 8:59 ` Mats Kärrman
2014-04-09 9:00 ` Javier Viguera [this message]
2014-04-09 9:11 ` Trevor Woerner
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=53450C29.5060202@digi.com \
--to=javier.viguera@digi.com \
--cc=openembedded-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