From: Carlos Santos <casantos@datacom.ind.br>
To: buildroot@busybox.net
Subject: [Buildroot] Build failure with 2017.05.1
Date: Wed, 19 Jul 2017 15:06:21 -0300 (BRT) [thread overview]
Message-ID: <1662234505.617742.1500487581506.JavaMail.zimbra@datacom.ind.br> (raw)
I got this error while building protobuf with Buildroot 2017.05.1:
>>> host-protobuf 3.2.0 Downloading
[...]
--2017-07-18 17:30:20-- https://github.com/google/protobuf/commit/416f90939d4de58fe1a4e2489120010313183291.patch
[...]
ERROR: 416f90939d4de58fe1a4e2489120010313183291.patch has wrong sha256 hash:
ERROR: expected: da80c39838515913633f4cbd875fdd4ad711be95c83a50ff5096b9f1254033b3
ERROR: got : 61e5b65b65e10f3ae7549b3a38eb30162ef298e387b1779d997ddf3633d63700
ERROR: Incomplete download, or man-in-the-middle (MITM) attack
Looks like the "patches downloaded from Github are not stable"
issue already fixed by Thomas Petazzoni in several recipes.
I solved the problem by means of a local change that brings
the patch in the tree.
Should I submit a patch specific for the 2017.05.x branch or it
would be preferable to cherry-pick the commits that bump protobuf
to v3.3.0 from master to 2017.05.x?
--
Carlos Santos (Casantos) - DATACOM, P&D
Rua Am?rica, 1000 - Eldorado do Sul, RS, Brasil - 92990-000
casantos at datacom.ind.br +55 51 3933.3000 ext. 3627
http://www.datacom.ind.br
next reply other threads:[~2017-07-19 18:06 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-07-19 18:06 Carlos Santos [this message]
2017-07-19 19:09 ` [Buildroot] Build failure with 2017.05.1 Thomas Petazzoni
2017-07-19 19:38 ` 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=1662234505.617742.1500487581506.JavaMail.zimbra@datacom.ind.br \
--to=casantos@datacom.ind.br \
--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