All of lore.kernel.org
 help / color / mirror / Atom feed
From: Arnout Vandecappelle (Essensium/Mind) <arnout@mind.be>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH v7 4/8] uclibc: update hash for arc
Date: Thu, 23 Apr 2015 00:08:37 +0200	[thread overview]
Message-ID: <1429740521-31943-5-git-send-email-arnout@mind.be> (raw)
In-Reply-To: <1429740521-31943-1-git-send-email-arnout@mind.be>

From: Arnout Vandecappelle <arnout@mind.be>

The old hash for 2014.08 was never updated. Since uclibc-arc-2014.12 is
downloaded from the github helper, it is converted into a 'none' hash.

Reordered the hashes so the none-hashes are together.

Signed-off-by: Arnout Vandecappelle (Essensium/Mind) <arnout@mind.be>
Acked-by: "Yann E. MORIN" <yann.morin.1998@free.fr>
Signed-off-by: Yann E. MORIN <yann.morin.1998@free.fr>
---
 package/uclibc/uclibc.hash | 6 +++---
 1 file changed, 3 insertions(+), 3 deletions(-)

diff --git a/package/uclibc/uclibc.hash b/package/uclibc/uclibc.hash
index 729c643..fe60291 100644
--- a/package/uclibc/uclibc.hash
+++ b/package/uclibc/uclibc.hash
@@ -1,11 +1,11 @@
 # Locally calculated after checking pgp signature
 sha256	62333167b79afb0b25a843513288c67b59547acf653e8fbe62ee64e71ebd1587	uClibc-0.9.33.2.tar.xz
 
-# Locally calculated
-sha256	0a9085a11615296cfe7783f16ff29073393eb330749947adece0eeddb31705a4	uClibc-arc-2014.08.tar.gz
-
 # From http://www.uclibc-ng.org/trac/
 sha256  7e92e99995daa634cbdc63c297784df6e8fe39cc1d3bbd2d37eb5c3ced8a86e5        uClibc-ng-1.0.2.tar.xz
 
+# No hash for the ARC variant, comes from the github-helper
+none	xxx	uClibc-arc-2014.12.tar.gz
+
 # No hash for this git snapshot
 none  xxx  uClibc-7bf35c8b7d4a1f97174eb49f47f33946b282114c.tar.gz
-- 
2.1.4

  parent reply	other threads:[~2015-04-22 22:08 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-04-22 22:08 [Buildroot] [PATCH v7 0/8] toolchain: better handle hashes (branch yem/dl-hash-toolchains) Arnout Vandecappelle
2015-04-22 22:08 ` [Buildroot] [PATCH v7 1/8] package/gcc: add hashes Arnout Vandecappelle
2015-04-23  5:36   ` Gustavo Zacarias
2015-04-22 22:08 ` [Buildroot] [PATCH v7 2/8] package/binutils: " Arnout Vandecappelle
2015-04-23  5:37   ` Gustavo Zacarias
2015-04-22 22:08 ` [Buildroot] [PATCH v7 3/8] package/uclibc: add missing hash for eXtensa Arnout Vandecappelle
2015-04-23  5:38   ` Gustavo Zacarias
2015-04-22 22:08 ` Arnout Vandecappelle [this message]
2015-04-23  5:48   ` [Buildroot] [PATCH v7 4/8] uclibc: update hash for arc Gustavo Zacarias
2015-04-22 22:08 ` [Buildroot] [PATCH v7 5/8] support/download: add possibility to not fail on missing hash Arnout Vandecappelle
2015-04-23  5:44   ` Gustavo Zacarias
2015-04-22 22:08 ` [Buildroot] [PATCH v7 6/8] toolchain/external: ignore missing hash for custom downloaded toolchain Arnout Vandecappelle
2015-04-23  5:43   ` Gustavo Zacarias
2015-04-22 22:08 ` [Buildroot] [PATCH v7 7/8] package/uclibc: ignore missing hash for snapshots Arnout Vandecappelle
2015-04-23  5:43   ` Gustavo Zacarias
2015-04-22 22:08 ` [Buildroot] [PATCH v7 8/8] support/download: restore mandatory check of hashes Arnout Vandecappelle
2015-04-23  5:44   ` Gustavo Zacarias
2015-04-25 12:26 ` [Buildroot] [PATCH v7 0/8] toolchain: better handle hashes (branch yem/dl-hash-toolchains) Thomas Petazzoni
2015-04-28 19:17   ` Arnout Vandecappelle

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=1429740521-31943-5-git-send-email-arnout@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.