Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Yann E. MORIN <yann.morin.1998@free.fr>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 0/3] support/download: be more aggressive on missing hashes (branch yem/dl-hash)
Date: Mon, 16 Mar 2015 23:41:41 +0100	[thread overview]
Message-ID: <cover.1426545571.git.yann.morin.1998@free.fr> (raw)

Hello All!

This series makes hashes mandatory when a .hash file exists.

Currently, we treat missing hashes as a mere warning. Unfortunately,
that often goes un-noticed by most users, and thus we get a lot of
package bumps that are missing the new hashes corresponding to the new
version.

We now make that a hard error, so users really notice something is
wrong.

Of course, if no .hash file exists, the behaviour is as yet unchanged.

Regards,
Yann E. MORIN.


The following changes since commit 2d05afa42792193fa392c9f5417e8effc73d1e38:

  cups: deprecate package due to security issues (2015-03-16 22:26:30 +0100)

are available in the git repository at:

  git://git.busybox.net/~ymorin/git/buildroot yem/dl-hash

for you to fetch changes up to e443dfcec4c084f823c718aa4c7740eddb3b628e:

  support/download: always fail when there's no hash (2015-03-16 23:33:48 +0100)

----------------------------------------------------------------
Yann E. MORIN (3):
      support/download: return different exit codes for different failures
      support/download: properly catch missing hashes
      support/download: always fail when there's no hash

 support/download/check-hash | 15 +++++++++------
 support/download/dl-wrapper | 11 ++++++++++-
 2 files changed, 19 insertions(+), 7 deletions(-)

-- 
.-----------------.--------------------.------------------.--------------------.
|  Yann E. MORIN  | Real-Time Embedded | /"\ ASCII RIBBON | Erics' conspiracy: |
| +33 662 376 056 | Software  Designer | \ / CAMPAIGN     |  ___               |
| +33 223 225 172 `------------.-------:  X  AGAINST      |  \e/  There is no  |
| http://ymorin.is-a-geek.org/ | _/*\_ | / \ HTML MAIL    |   v   conspiracy.  |
'------------------------------^-------^------------------^--------------------'

             reply	other threads:[~2015-03-16 22:41 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-03-16 22:41 Yann E. MORIN [this message]
2015-03-16 22:41 ` [Buildroot] [PATCH 1/3] support/download: return different exit codes for different failures Yann E. MORIN
2015-03-16 22:58   ` Samuel Martin
2015-03-16 22:41 ` [Buildroot] [PATCH 2/3] support/download: properly catch missing hashes Yann E. MORIN
2015-03-16 22:41 ` [Buildroot] [PATCH 3/3] support/download: always fail when there's no hash Yann E. MORIN
2015-03-16 23:04   ` Samuel Martin
2015-03-18 23:15   ` Arnout Vandecappelle
2015-03-19  0:06     ` Yann E. MORIN
2015-03-17  9:15 ` [Buildroot] [PATCH 0/3] support/download: be more aggressive on missing hashes (branch yem/dl-hash) 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=cover.1426545571.git.yann.morin.1998@free.fr \
    --to=yann.morin.1998@free.fr \
    --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