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] glibc: add version 2.24
Date: Fri, 5 Aug 2016 18:54:32 +0200	[thread overview]
Message-ID: <20160805185432.301e6a00@free-electrons.com> (raw)
In-Reply-To: <e6aa4d6c-3325-0f39-96b0-eb25db6a8574@gmail.com>

Hello,

On Fri, 5 Aug 2016 07:33:15 -0700, Khem Raj wrote:

> >  # Locally calculated after checking pgp signature (glibc)
> >  sha256	eb731406903befef1d8f878a46be75ef862b9056ab0cde1626d08a7a05328948	glibc-2.22.tar.xz
> >  sha256	94efeb00e4603c8546209cefb3e1a50a5315c86fa9b078b6fad758e187ce13e9	glibc-2.23.tar.xz
> > +sha256	99d4a3e8efd144d71488e478f62587578c0f4e1fa0b4eed47ee3d4975ebeb5d3	glibc-2.23.tar.xz  
> 
> typo. It should be 2.24

Right. And this means that the patch was not even built-tested, as
Buildroot bails out when there is a .hash file for a package, but no
hash matching the file that has been downloaded.

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

  reply	other threads:[~2016-08-05 16:54 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-08-05  8:59 [Buildroot] [PATCH] glibc: add version 2.24 Vicente Olivert Riera
2016-08-05 14:33 ` Khem Raj
2016-08-05 16:54   ` Thomas Petazzoni [this message]
2016-08-08  8:46     ` Vicente Olivert Riera
2016-08-05 16:53 ` Thomas Petazzoni
2016-08-05 20:58   ` Khem Raj
2016-08-05 21:17     ` Thomas Petazzoni
2016-08-05 21:25       ` Khem Raj
2016-08-05 21:30         ` Thomas Petazzoni
2016-08-08 16:42   ` Yann E. MORIN
2016-08-09  8:49     ` Thomas Petazzoni
2016-08-09 19:33       ` Yann E. MORIN
2016-08-09 19:42         ` Khem Raj
2016-08-09 19:56           ` 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=20160805185432.301e6a00@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