From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] [autobuild.buildroot.net] Build results for 2013-12-02
Date: Tue, 3 Dec 2013 15:25:41 +0100 [thread overview]
Message-ID: <20131203152541.47e942be@skate> (raw)
In-Reply-To: <529DE716.1000205@zacarias.com.ar>
Dear Gustavo Zacarias,
On Tue, 03 Dec 2013 11:13:42 -0300, Gustavo Zacarias wrote:
> > This failure is caused by another failure on gnutls package. This
> > problem has already fixed upstream so it will be available on the
> > next gnutls release:
> > https://gitorious.org/gnutls/gnutls/commit/346e323228f5cc71664c2f49541f816f88914342
>
> My fault for bumping gnutls :)
> I'm waiting for a new release since the patchset is big, otherwise it
> can be reverted to 3.2.6 since it's not a security bump.
I think reverting would be good, so that we no longer have the
autobuilder failures, and we can see if there are other problems
instead of falling many times into the gnutls issue.
Of course, as soon as a new release fixing the problem is around, we
can bump.
Thomas
--
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux, Kernel and Android engineering
http://free-electrons.com
next prev parent reply other threads:[~2013-12-03 14:25 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-12-03 7:30 [Buildroot] [autobuild.buildroot.net] Build results for 2013-12-02 Thomas Petazzoni
2013-12-03 14:04 ` Vicente Olivert Riera
2013-12-03 14:13 ` Gustavo Zacarias
2013-12-03 14:25 ` Thomas Petazzoni [this message]
2013-12-03 18:12 ` [Buildroot] [RFC] makefile ?= behavior Matthew Weber
2013-12-03 18:23 ` Yann E. MORIN
2013-12-03 18:32 ` Matthew Weber
2013-12-03 21:55 ` [Buildroot] [autobuild.buildroot.net] Build results for 2013-12-02 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=20131203152541.47e942be@skate \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox