From: Arnout Vandecappelle <arnout@mind.be>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 1/1] package/flot: update hash
Date: Sun, 31 Jan 2016 21:22:54 +0100 [thread overview]
Message-ID: <56AE6D1E.6030109@mind.be> (raw)
In-Reply-To: <1454235889-11021-1-git-send-email-bernd.kuhls@t-online.de>
On 31-01-16 11:24, Bernd Kuhls wrote:
> Upstream apparently updated their tarball
> http://thread.gmane.org/gmane.comp.lib.uclibc.buildroot/122226/focus=138335
>
> Issue reported upstream: https://github.com/flot/flot/issues/1484
>
> Signed-off-by: Bernd Kuhls <bernd.kuhls@t-online.de>
Looks like it's just the OS-X metadata junk that has been modified, so this
change is indeed harmless. I verified the new hash as well so
Acked-by: Arnout Vandecappelle (Essensium/Mind) <arnout@mind.be>
Regards,
Arnout
> ---
> package/flot/flot.hash | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/package/flot/flot.hash b/package/flot/flot.hash
> index 9bf348a..cb9f9ec 100644
> --- a/package/flot/flot.hash
> +++ b/package/flot/flot.hash
> @@ -1,2 +1,2 @@
> # Locally calculated
> -sha256 d6bddb781ce8ab8bba82c535a0767c22e606cabd9dbb484027b8ff375a193952 flot-0.8.3.tar.gz
> +sha256 ef9a873befe3ff5ea42ebf1c3657887265a1717744ca8ed0c2bd3dd736d16b21 flot-0.8.3.tar.gz
>
--
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: 7493 020B C7E3 8618 8DEC 222C 82EB F404 F9AC 0DDF
next prev parent reply other threads:[~2016-01-31 20:22 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-01-31 10:24 [Buildroot] [PATCH 1/1] package/flot: update hash Bernd Kuhls
2016-01-31 20:22 ` Arnout Vandecappelle [this message]
2016-01-31 22:49 ` 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=56AE6D1E.6030109@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.