From: Arnout Vandecappelle <arnout@mind.be>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 3/3] support/download: always fail when there's no hash
Date: Thu, 19 Mar 2015 00:15:39 +0100 [thread overview]
Message-ID: <550A071B.7000000@mind.be> (raw)
In-Reply-To: <e443dfcec4c084f823c718aa4c7740eddb3b628e.1426545571.git.yann.morin.1998@free.fr>
On 16/03/15 23:41, Yann E. MORIN wrote:
> At the time we introduced hashes, we did not want to be too harsh in the
> beginning, and give people some time to adapt and accept to hashes. So
> we so far only whined^Wwarned about a missing hash file.
>
> Some time has passed now, and people are still missing updating hashes
> when bumping packages.
>
> Let's make that warning a little bit more annoying...
If you ever revive this series (which I think would be a good idea), don't
forget to remove the reference to BR2_ENFORCE_CHECK_HASH from the manual as well.
Regards,
Arnout
>
> Signed-off-by: "Yann E. MORIN" <yann.morin.1998@free.fr>
> Cc: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
> ---
> support/download/check-hash | 8 ++------
> 1 file changed, 2 insertions(+), 6 deletions(-)
>
> diff --git a/support/download/check-hash b/support/download/check-hash
> index 4cc62f3..7971c38 100755
> --- a/support/download/check-hash
> +++ b/support/download/check-hash
> @@ -88,10 +88,6 @@ while read t h f; do
> done <"${h_file}"
>
> if [ ${nb_checks} -eq 0 ]; then
> - if [ -n "${BR2_ENFORCE_CHECK_HASH}" ]; then
> - printf "ERROR: No hash found for %s\n" "${base}" >&2
> - exit 2
> - else
> - printf "WARNING: No hash found for %s\n" "${base}" >&2
> - fi
> + printf "ERROR: No hash found for %s\n" "${base}" >&2
> + exit 2
> fi
>
--
Arnout Vandecappelle arnout at mind be
Senior Embedded Software Architect +32-16-286500
Essensium/Mind http://www.mind.be
G.Geenslaan 9, 3001 Leuven, Belgium BE 872 984 063 RPR Leuven
LinkedIn profile: http://www.linkedin.com/in/arnoutvandecappelle
GPG fingerprint: 7CB5 E4CC 6C2E EFD4 6E3D A754 F963 ECAB 2450 2F1F
next prev parent reply other threads:[~2015-03-18 23:15 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-03-16 22:41 [Buildroot] [PATCH 0/3] support/download: be more aggressive on missing hashes (branch yem/dl-hash) Yann E. MORIN
2015-03-16 22:41 ` [Buildroot] [PATCH 1/3] support/download: return different exit codes for different failures Yann E. MORIN
2015-03-16 22:58 ` Samuel Martin
2015-03-16 22:41 ` [Buildroot] [PATCH 2/3] support/download: properly catch missing hashes Yann E. MORIN
2015-03-16 22:41 ` [Buildroot] [PATCH 3/3] support/download: always fail when there's no hash Yann E. MORIN
2015-03-16 23:04 ` Samuel Martin
2015-03-18 23:15 ` Arnout Vandecappelle [this message]
2015-03-19 0:06 ` Yann E. MORIN
2015-03-17 9:15 ` [Buildroot] [PATCH 0/3] support/download: be more aggressive on missing hashes (branch yem/dl-hash) Yann E. MORIN
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=550A071B.7000000@mind.be \
--to=arnout@mind.be \
--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 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.