[#61822] Plan Developers Meeting Japan April 2014 — Zachary Scott <e@...>
I would like to request developers meeting around April 17 or 18 in this mo=
14 messages
2014/04/03
[#61825] Re: Plan Developers Meeting Japan April 2014
— Urabe Shyouhei <shyouhei@...>
2014/04/03
It's good if we have a meeting then.
[#61826] Re: Plan Developers Meeting Japan April 2014
— Zachary Scott <e@...>
2014/04/03
Regarding openssl issues, I=E2=80=99ve discussed possible meeting time with=
[#61833] Re: Plan Developers Meeting Japan April 2014
— Martin Bo煬et <martin.bosslet@...>
2014/04/03
Hi,
[#61847] Re: Plan Developers Meeting Japan April 2014
— Eric Wong <normalperson@...>
2014/04/03
Martin Boテ殕et <martin.bosslet@gmail.com> wrote:
[#61849] Re: Plan Developers Meeting Japan April 2014
— Zachary Scott <e@...>
2014/04/04
I will post summary of meeting on Google docs after the meeting.
[#61852] Re: Plan Developers Meeting Japan April 2014
— Eric Wong <normalperson@...>
2014/04/04
Zachary Scott <e@zzak.io> wrote:
[#61860] Re: Plan Developers Meeting Japan April 2014
— Zachary Scott <e@...>
2014/04/04
I=E2=80=99m ok with redmine, thanks for bringing up your concern!
[#62076] Candidacy to 2.1 branch maintainer. — Tomoyuki Chikanaga <nagachika00@...>
Hello,
7 messages
2014/04/17
[#62078] Re: Candidacy to 2.1 branch maintainer.
— SHIBATA Hiroshi <shibata.hiroshi@...>
2014/04/17
> And does anyone have counter proposal for 2.1 maintenance?
[ruby-core:61817] Re: ruby snapshot and openssl problems
From:
Joel VanderWerf <joelvanderwerf@...>
Date:
2014-04-03 02:52:09 UTC
List:
ruby-core #61817
On 04/02/2014 03:31 PM, Eric Wong wrote: > Joel VanderWerf <joelvanderwerf@gmail.com> wrote: >> Trying to build today's snapshot (ruby-2.2.0-r45509), and: > > This seems to be a bug with r45509. Reverting it helps, but there's > still warnings from r45508. > Cc-ing ruby-core. Turns out I can build the *stable* snapshot (ruby 2.1.2p80 (2014-03-01 revision 45231) [x86_64-linux]), and I can reproduce my segfault with that. The segfault (not related to openssl, AFAIK) is why I was trying to build the snapshot, to make sure it hadn't been fixed since 2.1. Still have to isolate it reliably so that it is reportable. It's probably in rbtree.