From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH] boot/uboot: add hash for 2012.07
Date: Sun, 26 Apr 2015 22:27:55 +0200 [thread overview]
Message-ID: <20150426222755.437ae3fe@free-electrons.com> (raw)
In-Reply-To: <1430078172-8136-1-git-send-email-vincent.stehle@laposte.net>
Vincent, Yann,
On Sun, 26 Apr 2015 21:56:12 +0200, Vincent Stehle wrote:
> From: Vincent Stehl? <vincent.stehle@laposte.net>
>
> To repair the build of pandaboard_defconfig.
>
> Signed-off-by: Vincent Stehl? <vincent.stehle@laposte.net>
> ---
> boot/uboot/uboot.hash | 1 +
> 1 file changed, 1 insertion(+)
>
> diff --git a/boot/uboot/uboot.hash b/boot/uboot/uboot.hash
> index 9cc96f6..9def045 100644
> --- a/boot/uboot/uboot.hash
> +++ b/boot/uboot/uboot.hash
> @@ -1,2 +1,3 @@
> # Locally computed:
> +sha256 e08e20a6979bfca6eebb9a2b0e42aa4416af3d796332fd63a3470495a089d496 u-boot-2012.07.tar.bz2
> sha256 0a1a70df586655f527befa6f12e184e96ed61b126e5a567382321b17200f5d60 u-boot-2015.04.tar.bz2
The problem indeed exists, but this is not the right solution. The
right solution is to use BR_NO_CHECK_HASH_FOR. Yann, can you look at
all the packages that may use custom versions (U-Boot, Barebox,
kernel, etc.) and do the necessary BR_NO_CHECK_HASH_FOR handling?
Thanks a lot!
Thomas
--
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux, Kernel and Android engineering
http://free-electrons.com
next prev parent reply other threads:[~2015-04-26 20:27 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-04-26 19:56 [Buildroot] [PATCH] boot/uboot: add hash for 2012.07 Vincent Stehle
2015-04-26 20:27 ` Thomas Petazzoni [this message]
2015-04-26 21:33 ` Yann E. MORIN
2015-04-28 8:03 ` Thomas Petazzoni
2015-04-28 9:52 ` Yann E. MORIN
2015-04-28 14:58 ` Thomas Petazzoni
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=20150426222755.437ae3fe@free-electrons.com \
--to=thomas.petazzoni@free-electrons.com \
--cc=buildroot@busybox.net \
/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