From: Gustavo Zacarias <gustavo@zacarias.com.ar>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH] ruby: security bump to version 2.1.4
Date: Tue, 04 Nov 2014 13:44:18 -0300 [thread overview]
Message-ID: <54590262.7010101@zacarias.com.ar> (raw)
In-Reply-To: <87y4rs0w4c.fsf@dell.be.48ers.dk>
On 11/03/2014 07:14 PM, Peter Korsgaard wrote:
> I know it wasn't caused by this bump, but we have a number of autobuild
> issues related to RUBY_EXEC_PREFIX. Could you perhaps take a look
> (ignore the bfin ones)?
>
> http://autobuild.buildroot.net/?reason=ruby-2.1.4
> http://autobuild.buildroot.net/?reason=ruby-2.1.3
Hi.
I'm unable to reproduce it.
And it seems to be limited to failures on gcc16 (the 2.1.3 bfin failures
are a different issue).
So i think it's something there since i've tested on a very old/bare
debian chroot here. Possibly a candidate for blacklisting.
Regards.
prev parent reply other threads:[~2014-11-04 16:44 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-10-27 21:13 [Buildroot] [PATCH] ruby: security bump to version 2.1.4 Gustavo Zacarias
2014-11-03 22:14 ` Peter Korsgaard
2014-11-04 16:44 ` Gustavo Zacarias [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=54590262.7010101@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