From: Richard Purdie <richard.purdie@linuxfoundation.org>
To: Khem Raj <raj.khem@gmail.com>, openembedded-core@lists.openembedded.org
Subject: Re: [PATCH] boost: Fix SRC_URI checksums
Date: Sun, 30 Oct 2016 16:40:29 +0000 [thread overview]
Message-ID: <1477845629.23123.20.camel@linuxfoundation.org> (raw)
In-Reply-To: <20161029194615.19954-1-raj.khem@gmail.com>
On Sat, 2016-10-29 at 12:46 -0700, Khem Raj wrote:
> Signed-off-by: Khem Raj <raj.khem@gmail.com>
Why, what happened?
Cheers,
Richard
> ---
> meta/recipes-support/boost/boost-1.62.0.inc | 4 ++--
> 1 file changed, 2 insertions(+), 2 deletions(-)
>
> diff --git a/meta/recipes-support/boost/boost-1.62.0.inc
> b/meta/recipes-support/boost/boost-1.62.0.inc
> index a097ea1..1144ac9 100644
> --- a/meta/recipes-support/boost/boost-1.62.0.inc
> +++ b/meta/recipes-support/boost/boost-1.62.0.inc
> @@ -13,7 +13,7 @@ BOOST_P = "boost_${BOOST_VER}"
>
> SRC_URI = "${SOURCEFORGE_MIRROR}/boost/${BOOST_P}.tar.bz2"
>
> -SRC_URI[md5sum] = "7ef085456c48c49a7fe8237f07e5f674"
> -SRC_URI[sha256sum] =
> "bce80293052e2d6230f1bec9b7524b33412e4fb26e9723460a0f362ac15b7acb"
> +SRC_URI[md5sum] = "21b799e5d35ba2beef75b225deaf199a"
> +SRC_URI[sha256sum] =
> "a715dc2adff2d451719352b1e863d78cbb100a03f7ed76097c89b9016c59091e"
>
> S = "${WORKDIR}/${BOOST_P}"
> --
> 2.10.1
>
next prev parent reply other threads:[~2016-10-30 16:40 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-10-29 19:46 [PATCH] boost: Fix SRC_URI checksums Khem Raj
2016-10-30 16:40 ` Richard Purdie [this message]
2016-10-30 17:39 ` Khem Raj
2016-10-31 3:27 ` Paul Eggleton
2016-10-31 3:45 ` Paul Eggleton
2016-10-31 12:53 ` Alexander Kanavin
2016-10-31 16:22 ` Khem Raj
2016-11-01 12:40 ` Alexander Kanavin
2016-11-01 16:06 ` Khem Raj
2016-11-01 16:33 ` Alexander Kanavin
2016-11-01 16:45 ` Khem Raj
2016-11-02 2:43 ` Paul Eggleton
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=1477845629.23123.20.camel@linuxfoundation.org \
--to=richard.purdie@linuxfoundation.org \
--cc=openembedded-core@lists.openembedded.org \
--cc=raj.khem@gmail.com \
/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