From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH v2] package: protobuf, python-protobuf: bump to v3.3.0
Date: Fri, 12 May 2017 10:07:57 +0200 [thread overview]
Message-ID: <20170512100757.3e865c73@free-electrons.com> (raw)
In-Reply-To: <20170512073503.601-1-mrugiero@gmail.com>
Hello,
On Fri, 12 May 2017 04:35:03 -0300, Mario J. Rugiero wrote:
> Includes upstream patch working around a gcc bug which got fixed in version 4.5.0.
>
> Fixes:
> http://autobuild.buildroot.org/results/77d/77dbb6bbbc0ea9e9bcdd22b10011ef9728c20d54/
> http://autobuild.buildroot.org/results/21f/21f5e1ea4f37e1d174604d6da78c0e916c89f1e3/
> http://autobuild.buildroot.org/results/24e/24e880086c87d40b5d79a90d805acc75b33d484c/
>
> Tested with:
> qemu_aarch64_virt_defconfig
>
> Signed-off-by: Mario J. Rugiero <mrugiero@gmail.com>
OK, but you just changed the hash... why did the hash change in the
first place, between the original 3.3.0 and the new 3.3.0 version ?
Did upstream re-upload a different tarball ? If that's the case, could
you tell upstream that this is really really bad ?
Thomas
--
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux and Kernel engineering
http://free-electrons.com
next prev parent reply other threads:[~2017-05-12 8:07 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-05-03 20:59 [Buildroot] [PATCH v2] package: protobuf, python-protobuf: bump to v3.3.0 Mario J. Rugiero
2017-05-04 12:56 ` Thomas Petazzoni
2017-05-04 13:34 ` Mario Rugiero
2017-05-05 17:24 ` Mario Rugiero
2017-05-05 18:20 ` Thomas Petazzoni
2017-05-05 18:27 ` Mario Rugiero
2017-05-11 21:00 ` Thomas Petazzoni
2017-05-12 7:35 ` Mario J. Rugiero
2017-05-12 8:07 ` Thomas Petazzoni [this message]
2017-05-12 8:13 ` Mario Rugiero
2017-05-12 20:01 ` Mario Rugiero
2017-07-02 8:31 ` 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=20170512100757.3e865c73@free-electrons.com \
--to=thomas.petazzoni@free-electrons.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.