From: "Marcin Niestrój" <m.niestroj@grinn-global.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH v2] linux-firmware: bump version to latest 1baa348
Date: Tue, 13 Nov 2018 22:34:12 +0100 [thread overview]
Message-ID: <87a7mcsluz.fsf@grinn-global.com> (raw)
In-Reply-To: <20181113210216.37879bd4@windsurf>
Hi,
Thomas Petazzoni <thomas.petazzoni@bootlin.com> writes:
> Hello,
>
> On Tue, 13 Nov 2018 18:20:57 +0100, Marcin Niestr?j wrote:
>
>> I have investigated the issue on my side. It turns out that gzip is
>> really the issue here.
>
> Thanks for the additional investigation!
Some new findings now. It turned out that I actually used pigz instead
of gzip. It was not directly clear, because I had PATH variable
prepended with a directory containing "gzip -> /usr/bin/pigz". I have
set this up ~3 years ago and totally forgot about that. Sorry for
misleading that gzip version / patch could be the reason of wrong hash
in my case.
I need to really go through all the patches that got applied to
master...
>
>> You can find differences in package here:
>> https://git.archlinux.org/svntogit/packages.git/log/trunk?h=packages/gzip
>>
>> I have also checked output of gzip command on another PC with pigz
>> configured as gzip drop-in replacement. It outputs even different file,
>> with different sha256 hash.
>>
>> I think the overall conclusion is that a host-gzip package is needed,
>> just like host-tar. In the meantime I will send v3 of this patch with
>> proper hash (the same as you calculated above).
--
Marcin Niestr?j
prev parent reply other threads:[~2018-11-13 21:34 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-11-08 15:33 [Buildroot] [PATCH v2] linux-firmware: bump version to latest 1baa348 Marcin Niestroj
2018-11-09 20:57 ` Thomas Petazzoni
2018-11-09 21:06 ` Yann E. MORIN
2018-11-13 17:20 ` Marcin Niestrój
2018-11-13 17:32 ` Marcin Niestrój
2018-11-13 20:02 ` Thomas Petazzoni
2018-11-13 20:29 ` Yann E. MORIN
2018-11-13 20:57 ` Thomas Petazzoni
2018-11-13 23:54 ` Arnout Vandecappelle
2018-11-15 19:05 ` Yann E. MORIN
2018-11-16 8:35 ` Thomas Petazzoni
2018-11-20 18:50 ` Yann E. MORIN
2018-11-20 23:47 ` Arnout Vandecappelle
2018-11-21 7:13 ` Peter Korsgaard
2018-11-13 21:34 ` Marcin Niestrój [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=87a7mcsluz.fsf@grinn-global.com \
--to=m.niestroj@grinn-global.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