From: Yann E. MORIN <yann.morin.1998@free.fr>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 1/1] mongoose: fix hash
Date: Sun, 9 Sep 2018 12:20:28 +0200 [thread overview]
Message-ID: <20180909102028.GF2841@scaer> (raw)
In-Reply-To: <20180907091210.6ad78022@windsurf.home>
Fabrice, Thomas, All,
On 2018-09-07 09:12 +0200, Thomas Petazzoni spake thusly:
> On Fri, 07 Sep 2018 06:35:21 +0300, Baruch Siach wrote:
> > But the current github download is indeed different. Not sure what went
> > wrong here, but this description is not correct.
> I saw Yann and Peter talking about github tarballs having changed again:
>
> 18:29 < Jacmet> hmm, looks like github tarballs again changed content :/
> 18:29 < Jacmet> http://autobuild.buildroot.net/results/599/599920bc0a5821fd3fb0a028574a25a22e12430f/build-end.log
> 18:42 < y_morin> Jacmet: At the same time, the fallback to s.b.o timeout, so maybe it is not a github issue either?
> 18:43 < Jacmet> y_morin: well, it did get a tarball from github and the hash didn't match
> 18:43 < y_morin> Jacmet: Arg, indeed. I even had another sha256 than the one in the report.
> 18:44 < Jacmet> y_morin: and downloading it from github here I also get the same (wrong) hash
That does not happen for all archives, though... :-/
And I can see that indeed the generated tarball is different from the
one on s.b.o.: it slightly differ in the way directory entries are
stored... Except for that, the actual content is the same.
Regards,
Yann E. MORIN.
--
.-----------------.--------------------.------------------.--------------------.
| 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-09-09 10:20 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-09-06 21:42 [Buildroot] [PATCH 1/1] mongoose: fix hash Fabrice Fontaine
2018-09-07 3:35 ` Baruch Siach
2018-09-07 7:12 ` Thomas Petazzoni
2018-09-09 10:20 ` Yann E. MORIN [this message]
2018-10-21 16:06 ` Thomas Petazzoni
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=20180909102028.GF2841@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.