From: Peter Korsgaard <peter@korsgaard.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 1/1] Update github hashes
Date: Wed, 20 Sep 2017 19:52:50 +0200 [thread overview]
Message-ID: <87fubhxnnx.fsf@dell.be.48ers.dk> (raw)
In-Reply-To: <20170920112825.3971-1-bernd.kuhls@t-online.de> (Bernd Kuhls's message of "Wed, 20 Sep 2017 13:28:25 +0200")
>>>>> "Bernd" == Bernd Kuhls <bernd.kuhls@t-online.de> writes:
> It seems github now sometimes provides slightly changed tarballs which
> produce a different sha256 hash than before. Fix the hashes of the
> affected packages to avoid downloading from sources.buildroot.net.
> Signed-off-by: Bernd Kuhls <bernd.kuhls@t-online.de>
:/
I'm not sure updating the hashes is the correct thing to do. Sources.b.o
runs 'make source' from the 2017.02.x and master branches to keep it
uptodate, and E.G. freerdp hasn't been updated since 2017.02, so it will
break hard for 2017.02.x users if we change it.
Falling back to s.b.o is not such a bad thing, so I think we can wait
with fixing up the hashes until the packages get bumped.
In the mean time I will try to figure out who to contact at github to
ask about the change.
--
Bye, Peter Korsgaard
next prev parent reply other threads:[~2017-09-20 17:52 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-09-20 11:28 [Buildroot] [PATCH 1/1] Update github hashes Bernd Kuhls
2017-09-20 17:35 ` Yann E. MORIN
2017-09-20 17:52 ` Peter Korsgaard [this message]
2017-09-20 18:03 ` Matthew Weber
2017-09-20 18:29 ` Bernd Kuhls
2017-09-21 7:23 ` Peter Korsgaard
2017-09-21 9:17 ` Bernd Kuhls
2017-09-21 9:32 ` Peter Korsgaard
2017-09-21 20:35 ` Arnout Vandecappelle
2017-09-21 21:23 ` Peter Korsgaard
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=87fubhxnnx.fsf@dell.be.48ers.dk \
--to=peter@korsgaard.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 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.