From: Yann E. MORIN <yann.morin.1998@free.fr>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH v2] linux-firmware: bump version to latest 1baa348
Date: Fri, 9 Nov 2018 22:06:10 +0100 [thread overview]
Message-ID: <20181109210610.GB2445@scaer> (raw)
In-Reply-To: <20181109215700.6b8dc6af@windsurf>
Marcin, Thomas, All,
On 2018-11-09 21:57 +0100, Thomas Petazzoni spake thusly:
> On Thu, 8 Nov 2018 16:33:22 +0100, Marcin Niestroj wrote:
>
> > -sha256 b279ca4d086887c2efab13e28a7ca36e409410d3df38a62d7c7b5799ee3de916 linux-firmware-44d4fca9922a252a0bd81f6307bcc072a78da54a.tar.gz
> > +sha256 3e4fcbac18990a14d52159fefdc70081a56c5244adba28b14242e159a748e755 linux-firmware-1baa34868b2c0a004dc595b20678145e3fff83e7.tar.gz
>
> I am sorry, but this hash is still not good for me, I get:
>
> 5c636765fd1ac638176893feccfd4a4854f59fc3d01b38f3ccdbb89bd5bb6ef1
>
> I.e:
>
> ERROR: linux-firmware-1baa34868b2c0a004dc595b20678145e3fff83e7.tar.gz has wrong sha256 hash:
> ERROR: expected: 3e4fcbac18990a14d52159fefdc70081a56c5244adba28b14242e159a748e755
> ERROR: got : 5c636765fd1ac638176893feccfd4a4854f59fc3d01b38f3ccdbb89bd5bb6ef1
>
> And this morning, Yann E. Morin reported having the same hash as me:
>
> 08:07 < y_morin> kos_tom: I also have a different hash here.
> 08:10 < y_morin> kos_tom: FTR, I got: 5c636765fd1ac638176893feccfd4a4854f59fc3d01b38f3ccdbb89bd5bb6ef1
Right.
> My system tar is 1.29, which is considered as a "good" version by
> support/dependencies/check-host-tar.sh. I have nonetheless forced
> building host-tar, and I still get the same hash.
Recently, another user reported hash issues as well, and it turned out
that they had changed gzip to be really pigz (a parallel gzip). Can you
check if that is not your case too?
Regards,
Yann E. MORIN.
> I have uploaded the tarball at
> https://bootlin.com/~thomas/pub/linux-firmware-1baa34868b2c0a004dc595b20678145e3fff83e7.tar.gz.
> Could you upload the tarball that was generated on your side so that we
> can compare them, and see where the problem lies ?
>
> Best regards,
>
> Thomas
> --
> Thomas Petazzoni, CTO, Bootlin
> Embedded Linux and Kernel engineering
> https://bootlin.com
--
.-----------------.--------------------.------------------.--------------------.
| 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. |
'------------------------------^-------^------------------^--------------------'
next prev parent reply other threads:[~2018-11-09 21:06 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 [this message]
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
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=20181109210610.GB2445@scaer \
--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