Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Thomas Petazzoni <thomas.petazzoni@bootlin.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 1/1] mongoose: fix hash
Date: Fri, 7 Sep 2018 09:12:10 +0200	[thread overview]
Message-ID: <20180907091210.6ad78022@windsurf.home> (raw)
In-Reply-To: <87musu3rpi.fsf@tkos.co.il>

Hello,

On Fri, 07 Sep 2018 06:35:21 +0300, Baruch Siach wrote:

> Fabrice Fontaine writes:
> > When bumping to version 6.7, hash was not updated  
> 
> Commit 965c5ca57d3 (mongoose: bump to version 6.7) from April 2017, did
> update the hash to its current value. You can find a tarball with this
> hash at
> 
>   http://sources.buildroot.net/mongoose-6.7.tar.gz
> 
> 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

Best regards,

Thomas
-- 
Thomas Petazzoni, CTO, Bootlin
Embedded Linux and Kernel engineering
https://bootlin.com

  reply	other threads:[~2018-09-07  7:12 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 [this message]
2018-09-09 10:20     ` Yann E. MORIN
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=20180907091210.6ad78022@windsurf.home \
    --to=thomas.petazzoni@bootlin.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