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] [PATCH 1/3 v2] package: add hashes for SourceForge-hosted packages
Date: Sun, 28 Dec 2014 22:34:21 +0100	[thread overview]
Message-ID: <20141228223421.36ad48fd@free-electrons.com> (raw)
In-Reply-To: <d23cfbca4078af76c4bbee70ed02006124c5d0c7.1419768498.git.yann.morin.1998@free.fr>

Dear Yann E. MORIN,

On Sun, 28 Dec 2014 13:19:29 +0100, Yann E. MORIN wrote:
> Since SourceForge sometimes serves us faulty tarballs, we can tons of
> autobuild failures:
>     http://autobuild.buildroot.org/results/9fb/9fba5bf086a4e7a29e5f7156ec43847db7aacfc4/
>     http://autobuild.buildroot.org/results/6c8/6c837b244c45ac3b3a887734a371cd6d226cf216/
>     ...
> 
> Fix that by adding hash files for all SourceForge-hosted packages (thos
> etht did not already have it).
> 
> We normally prefer to use hashes published by upstream, but hunting them
> all one by one is a tedious task, so those hashes were all locally
> computed with a script that searched for SF-hosted packages, downloades
> the associated tarball, computed the hash, and stored it in the
> corresponding .hash file.
> 
> Also, SF publishes sha1 hashes, while I used the stronger sha256, since
> sha1 is now considered to be relatively weak.
> 
> Signed-off-by: "Yann E. MORIN" <yann.morin.1998@free.fr>
> Cc: Peter Korsgaard <jacmet@uclibc.org>
> Cc: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
> Cc: Maxime Hadjinlian <maxime.hadjinlian@gmail.com>
> Cc: Richard Braun <rbraun@sceen.net>
> Cc: Nathaniel Roach <nroach44@gmail.com>

Applied, thanks. I've verified that the hashes were matching here by
running:

make $(git show | grep "^+++" | sed 's%.*package/\([^/]*\)/.*%\1-extract%' | sed 's/scons-extract/host-scons-extract/' | sed 's/swig-extract/host-swig-extract/' | sed 's/upx-extract/host-upx-extract/' | tr "\n" " ")

which ended successfully.

Thanks,

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

  reply	other threads:[~2014-12-28 21:34 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-12-28 12:19 [Buildroot] [PATCH 0/3 v2] Add a lot of hashes (branch yem/sf-hash) Yann E. MORIN
2014-12-28 12:19 ` [Buildroot] [PATCH 1/3 v2] package: add hashes for SourceForge-hosted packages Yann E. MORIN
2014-12-28 21:34   ` Thomas Petazzoni [this message]
2014-12-28 12:19 ` [Buildroot] [PATCH 2/3 v2] toolchain-external: add hashes for Blackfin toolchains Yann E. MORIN
2014-12-28 21:41   ` Thomas Petazzoni
2014-12-28 12:19 ` [Buildroot] [PATCH 3/3 v2] toolchain: add hashes for all remaining external toolchains Yann E. MORIN
2014-12-28 12:58   ` Thomas Petazzoni
2014-12-28 13:31     ` 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=20141228223421.36ad48fd@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