Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCHv2] [autobuild] package/bwm-ng: fix build failures with gcc-5
Date: Mon, 17 Aug 2015 22:34:18 +0200	[thread overview]
Message-ID: <20150817223418.6f75a2e6@free-electrons.com> (raw)
In-Reply-To: <1439736791-28748-1-git-send-email-yann.morin.1998@free.fr>

Dear Yann E. MORIN,

On Sun, 16 Aug 2015 16:53:11 +0200, Yann E. MORIN wrote:

> diff --git a/package/bwm-ng/bwm-ng.hash b/package/bwm-ng/bwm-ng.hash
> index 6bb8355..85f436f 100644
> --- a/package/bwm-ng/bwm-ng.hash
> +++ b/package/bwm-ng/bwm-ng.hash
> @@ -1,2 +1,4 @@
> -# Locally calculated
> -sha256  c1134358e268329d438b0996399003b0f0b966034fb4b5b138761c2f3c62ffdd  bwm-ng-0.6.tar.gz
> +# From: http://sourceforge.net/projects/bwmng/files/bwmng/0.6/
> +# sha1  9445885d05e2430ca174739e3aba343afce94076  bwm-ng-0.6.1.tar.gz
> +# Because we do not trust SF.net, locally computed sha256:
> +sha256  027cf3c960cd96fc9ffacdf7713df62d0fc55eeef4a1388289f8a62ae5e50df0  bwm-ng-0.6.1.tar.gz

I think this is silly. We should use both the sha1 provided by
sourceforge and a locally calculated sha256 hash.

Best regards,

Thomas
-- 
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux, Kernel and Android engineering
http://free-electrons.com

  reply	other threads:[~2015-08-17 20:34 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-08-16 14:53 [Buildroot] [PATCHv2] [autobuild] package/bwm-ng: fix build failures with gcc-5 Yann E. MORIN
2015-08-17 20:34 ` Thomas Petazzoni [this message]
2015-08-17 21:04   ` Yann E. MORIN
2015-08-18  8:33     ` Thomas Petazzoni
2015-08-18  9:16 ` 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=20150817223418.6f75a2e6@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