From: Peter Korsgaard <peter@korsgaard.com>
To: buildroot@busybox.net
Subject: [Buildroot] [autobuild.buildroot.net] Build results for 2017-04-27
Date: Fri, 28 Apr 2017 12:01:10 +0200 [thread overview]
Message-ID: <87shksj1g9.fsf@dell.be.48ers.dk> (raw)
In-Reply-To: <20170428110851.03eff198@free-electrons.com> (Thomas Petazzoni's message of "Fri, 28 Apr 2017 11:08:51 +0200")
>>>>> "Thomas" == Thomas Petazzoni <thomas.petazzoni@free-electrons.com> writes:
> Hello,
> On Fri, 28 Apr 2017 11:44:33 +0300, Baruch Siach wrote:
>> Incompatibility of ola with protobuf 3.2.0. An upstream issue[1] is open since
>> January.
>>
>> Should we revert the protobuf bump? Remove ola?
> Remove ola is I believe the right approach. According to the Github
> issue, Fedora has done the same thing.
> I believe it's more important to stay up-to-date with protobuf than it
> is to keep ola as a package, especially since ola is not used as a
> dependency for any other package.
> Maybe just mark it BROKEN for now?
Yes, I think that is the best way forward as well.
--
Bye, Peter Korsgaard
prev parent reply other threads:[~2017-04-28 10:01 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-04-28 6:28 [Buildroot] [autobuild.buildroot.net] Build results for 2017-04-27 Thomas Petazzoni
2017-04-28 8:44 ` Baruch Siach
2017-04-28 9:08 ` Thomas Petazzoni
2017-04-28 10:01 ` Peter Korsgaard [this message]
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=87shksj1g9.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox