From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH v7 0/8] toolchain: better handle hashes (branch yem/dl-hash-toolchains)
Date: Sat, 25 Apr 2015 14:26:34 +0200 [thread overview]
Message-ID: <20150425142634.516e800e@free-electrons.com> (raw)
In-Reply-To: <1429740521-31943-1-git-send-email-arnout@mind.be>
Hello,
On Thu, 23 Apr 2015 00:08:33 +0200, Arnout Vandecappelle
(Essensium/Mind) wrote:
> Arnout Vandecappelle (1):
> uclibc: update hash for arc
>
> Yann E. MORIN (7):
> package/gcc: add hashes
> package/binutils: add hashes
> package/uclibc: add missing hash for eXtensa
> support/download: add possibility to not fail on missing hash
> toolchain/external: ignore missing hash for custom downloaded toolchain
> package/uclibc: ignore missing hash for snapshots
> support/download: restore mandatory check of hashes
Series applied.
One thing that bothered me a little bit is that when the hash of the
tarball downloaded from upstream doesn't match the one we have in BR,
we gracefully fall back on downloading the tarball from
sources.buildroot.net.
This is good for users as it means their build succeeds. But not so
good from the point of view of noticing that upstream has for some
reason changed the tarball.
Any opinion about this?
Thomas
--
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux, Kernel and Android engineering
http://free-electrons.com
next prev parent reply other threads:[~2015-04-25 12:26 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 ` [Buildroot] [PATCH v7 4/8] uclibc: update hash for arc Arnout Vandecappelle
2015-04-23 5:48 ` 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 ` Thomas Petazzoni [this message]
2015-04-28 19:17 ` [Buildroot] [PATCH v7 0/8] toolchain: better handle hashes (branch yem/dl-hash-toolchains) 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=20150425142634.516e800e@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