From: "Jörg Krause" <joerg.krause@embedded.rocks>
To: buildroot@busybox.net
Subject: [Buildroot] linux-firmware: wrong sha256 hash
Date: Thu, 01 Feb 2018 08:54:13 +0100 [thread overview]
Message-ID: <1517471653.2404.1.camel@embedded.rocks> (raw)
In-Reply-To: <20180131185016.3diheii3anpqrymi@tarshish>
Hi Baruch
On Wed, 2018-01-31 at 20:50 +0200, Baruch Siach wrote:
> Hi J?rg,
>
> On Wed, Jan 31, 2018 at 05:52:34PM +0100, J?rg Krause wrote:
> > looks like the hashes for the linux-firmware git repository have
> > changed:
>
> It seem like you were probably bitten by the --numeric-owner behaviour change
> in tar version 1.30. See the thread starting at:
>
> http://lists.busybox.net/pipermail/buildroot/2018-January/211222.html
Thanks! I somehow missed that discussion.
J?rg
prev parent reply other threads:[~2018-02-01 7:54 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-01-31 16:52 [Buildroot] linux-firmware: wrong sha256 hash Jörg Krause
2018-01-31 18:50 ` Baruch Siach
2018-02-01 7:54 ` Jörg Krause [this message]
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=1517471653.2404.1.camel@embedded.rocks \
--to=joerg.krause@embedded.rocks \
--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