Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Gustavo Zacarias <gustavo@zacarias.com.ar>
To: buildroot@busybox.net
Subject: [Buildroot] [autobuild.buildroot.net] Build results for 2013-12-02
Date: Tue, 03 Dec 2013 11:13:42 -0300	[thread overview]
Message-ID: <529DE716.1000205@zacarias.com.ar> (raw)
In-Reply-To: <529DE4FE.8020900@imgtec.com>

On 12/03/2013 11:04 AM, Vicente Olivert Riera wrote:

> On 12/03/2013 07:30 AM, Thomas Petazzoni wrote:
>> Build statistics for 2013-12-02
>> ===============================
> 
>> Detail of failures
>> ===================
> 
>>        mips |                 aiccu-20070115 | NOK |
>> http://autobuild.buildroot.net/results/d05e23031ea5542610c26c89908ae64c741fd330/
>>
> 
> 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.
Regards.

  reply	other threads:[~2013-12-03 14:13 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 [this message]
2013-12-03 14:25     ` Thomas Petazzoni
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=529DE716.1000205@zacarias.com.ar \
    --to=gustavo@zacarias.com.ar \
    --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