# Preparing 1.1.2 release **URL:** \ **Category:** IronRuby\ **Created:** [February 7, 2011, 4:59am UTC](https://www.ruby-forum.com/t/preparing-1-1-2-release/202826 "2011-02-07T04:59:46Z")\ **Posts on this page:** 12\ **Page:** 1
**Author:** ![dubstep](https://www.ruby-forum.com/letter_avatar_proxy/v4/letter/d/cdc98d/32.png) [@dubstep](https://www.ruby-forum.com/u/dubstep)\ **Post date:** [February 7, 2011, 4:59am UTC](https://www.ruby-forum.com/t/preparing-1-1-2-release/202826/1 "2011-02-07T04:59:46Z")
Preliminary binaries are here packaged as an .msi (hopefully, it’s accessible): [http://alturl.com/3xnzm](http://alturl.com/3xnzm) Let me know if there were any problems with the installation. Especially test various Gems - this release should fix the infamous “can’t convert NilClass into String” bug ([http://ironruby.codeplex.com/workitem/5728](http://ironruby.codeplex.com/workitem/5728), [http://ironruby.codeplex.com/workitem/5695](http://ironruby.codeplex.com/workitem/5695), etc.). (an alternative link to the .msi is [http://9qodxw.blu.livefilestore.com/y1pvmLNcFco8fyb3ow2A7mrDtNZ8oXH-yz2sNbCiJhvamDaDSSo3-6u1kEd97ivI9sV82s0ImyhZmdPZV0pyzxM4WxhTkm1vNJN/IronRuby.msi?download&psid=2](http://9qodxw.blu.livefilestore.com/y1pvmLNcFco8fyb3ow2A7mrDtNZ8oXH-yz2sNbCiJhvamDaDSSo3-6u1kEd97ivI9sV82s0ImyhZmdPZV0pyzxM4WxhTkm1vNJN/IronRuby.msi?download&psid=2)) Thanks, Tomas From: removed\_email\_address@domain.invalid [[mailto:removed\_email\_address@domain.invalid](mailto:removed_email_address@domain.invalid)] On Behalf Of Shay F. Sent: Tuesday, February 01, 2011 12:38 AM To: removed\_email\_address@domain.invalid Subject: Re: [Ironruby-core] [IronPython] Proposed Release Schedule for 2.7 I’d be happy to help. Let me know what needs to be done. Shay. On Tue, Feb 1, 2011 at 8:41 AM, Tomas M. \ wrote: It’s easy to build the msi’s and I’ll run IronRuby tests. I could use some help with IronRuby Tools testing. Tomas From: removed\_email\_address@domain.invalid[mailto:removed\_email\_address@domain.invalid](mailto:removed_email_address@domain.invalid) [[mailto:removed\_email\_address@domain.invalid](mailto:removed_email_address@domain.invalid)[mailto:removed\_email\_address@domain.invalid](mailto:removed_email_address@domain.invalid)] On Behalf Of Jimmy S. Sent: Monday, January 31, 2011 8:28 PM To: Discussion of IronPython Cc: removed\_email\_address@domain.invalid[mailto:removed\_email\_address@domain.invalid](mailto:removed_email_address@domain.invalid) Subject: Re: [IronPython] Proposed Release Schedule for 2.7 That schedule looks good for me too, and I can help get the releases out as well. ~Jimmy On Sun, Jan 30, 2011 at 3:37 PM, Tomas M. \ wrote: I propose we sync IronRuby releases with IronPython as follows: IronRuby - IronPython - date 1.1.2 - Beta 2 - February 6 none - RC1 - February 20 none - RC2 - February 27 1.1.3 - RTM - March 6 Tomas ---
**Author:** ![grujildo](https://www.ruby-forum.com/letter_avatar_proxy/v4/letter/g/94ad74/32.png) [@grujildo](https://www.ruby-forum.com/u/grujildo)\ **Post date:** [February 7, 2011, 1:42pm UTC](https://www.ruby-forum.com/t/preparing-1-1-2-release/202826/2 "2011-02-07T13:42:48Z")
Unfortunately none of the links are accessible… Regards Eduardo Tomas M. wrote in post #979978: > Preliminary binaries are here packaged as an .msi (hopefully, it’s > accessible): > > [http://alturl.com/3xnzm](http://alturl.com/3xnzm) > > Let me know if there were any problems with the installation. Especially > test various Gems - this release should fix the infamous “can’t convert > NilClass into String” bug ([http://ironruby.codeplex.com/workitem/5728](http://ironruby.codeplex.com/workitem/5728), > [http://ironruby.codeplex.com/workitem/5695](http://ironruby.codeplex.com/workitem/5695), etc.). > > (an alternative link to the .msi is [http://9qodxw.blu.livefilestore.com/y1pvmLNcFco8fyb3ow2A7mrDtNZ8oXH-yz2sNbCiJhvamDaDSSo3-6u1kEd97ivI9sV82s0ImyhZmdPZV0pyzxM4WxhTkm1vNJN/IronRuby.msi?download&psid=2](http://9qodxw.blu.livefilestore.com/y1pvmLNcFco8fyb3ow2A7mrDtNZ8oXH-yz2sNbCiJhvamDaDSSo3-6u1kEd97ivI9sV82s0ImyhZmdPZV0pyzxM4WxhTkm1vNJN/IronRuby.msi?download&psid=2)) > Thanks, > Tomas ---
**Author:** ![grujildo](https://www.ruby-forum.com/letter_avatar_proxy/v4/letter/g/94ad74/32.png) [@grujildo](https://www.ruby-forum.com/u/grujildo)\ **Post date:** [February 7, 2011, 6:56pm UTC](https://www.ruby-forum.com/t/preparing-1-1-2-release/202826/3 "2011-02-07T18:56:49Z")
Oops ☹ Let’s try again: [http://cid-b3ba7307194acfee.skydrive.live.com/self.aspx/IronRuby/IronRuby.msi](http://cid-b3ba7307194acfee.skydrive.live.com/self.aspx/IronRuby/IronRuby.msi) I have the binaries ready, will publish them in the evening unless there is some major issue. Tomas ---
**Author:** ![grujildo](https://www.ruby-forum.com/letter_avatar_proxy/v4/letter/g/94ad74/32.png) [@grujildo](https://www.ruby-forum.com/u/grujildo)\ **Post date:** [February 7, 2011, 8:13pm UTC](https://www.ruby-forum.com/t/preparing-1-1-2-release/202826/4 "2011-02-07T20:13:28Z")
Will this run on Mono or is .net 4.0 required? ---
**Author:** ![grujildo](https://www.ruby-forum.com/letter_avatar_proxy/v4/letter/g/94ad74/32.png) [@grujildo](https://www.ruby-forum.com/u/grujildo)\ **Post date:** [February 7, 2011, 11:14pm UTC](https://www.ruby-forum.com/t/preparing-1-1-2-release/202826/5 "2011-02-07T23:14:13Z")
Hi Tomas, I’m willing to try 1.1.2 a bit on Mac OS X if you’d like. How can I download it ? (the link you provided is a .msi only if I’m right ?) As well, I recall someone mentioning issues to ensure RVM would be able to automatically download it (maybe EULA agreement on codeplex that could not be skipped). This would definitely help people on non Windows machine try it it, as RVM is pretty standard amongst rubyists these days (outside Windows I mean). Let me know if I can help! – Thibaut ---
**Author:** ![grujildo](https://www.ruby-forum.com/letter_avatar_proxy/v4/letter/g/94ad74/32.png) [@grujildo](https://www.ruby-forum.com/u/grujildo)\ **Post date:** [February 7, 2011, 10:10pm UTC](https://www.ruby-forum.com/t/preparing-1-1-2-release/202826/6 "2011-02-07T22:10:44Z")
IronRuby 1.1.2 runs on Mono, though there are some bugs in Mono that might cause issues in certain scenarios. The best Mono version to try it on would be 2.10. The .msi requires .NET 4.0, a separate zip package with raw dlls will be available later today (you can always build from sources as well). I tested the binaries on Mono 2.10 RC2 on Windows. If you have non-Windows systems, please, try 1.1.2 out, report bugs and/or submit fixes! Thanks, Tomas ---
**Author:** ![grujildo](https://www.ruby-forum.com/letter_avatar_proxy/v4/letter/g/94ad74/32.png) [@grujildo](https://www.ruby-forum.com/u/grujildo)\ **Post date:** [February 7, 2011, 11:39pm UTC](https://www.ruby-forum.com/t/preparing-1-1-2-release/202826/7 "2011-02-07T23:39:56Z")
> I’m cloning it right now (then I’ll look where is Ruby.sln, because I have no idea yet :-)). I’ll report back here after doing a few basic tests. > Having a script that takes dlls built by xbuild and packages them for Mac > would be great. Any volunteers? I can try that out next week if all goes well with my current website launch 🙂 But yes, I think I’ll be able to help here. – Thibaut ---
**Author:** ![grujildo](https://www.ruby-forum.com/letter_avatar_proxy/v4/letter/g/94ad74/32.png) [@grujildo](https://www.ruby-forum.com/u/grujildo)\ **Post date:** [February 7, 2011, 11:27pm UTC](https://www.ruby-forum.com/t/preparing-1-1-2-release/202826/8 "2011-02-07T23:27:23Z")
I’ll publish the binaries in the evening today. That said, there wasn’t really any testing on non-Windows platform at all that I know of. So it might be best to build a debug build from sources instead of using release build. Error stack traces will be better. Mono 2.10 RC2 is able to build Ruby.sln on Windows. It would be interesting to see if it works well on MacOS. Would you be willing to clone git repo and run “xbuild Ruby.sln”? You can then try to use the built binaries from Bin\Debug directory. Having a script that takes dlls built by xbuild and packages them for Mac would be great. Any volunteers? Tomas From: removed\_email\_address@domain.invalid [[mailto:removed\_email\_address@domain.invalid](mailto:removed_email_address@domain.invalid)] On Behalf Of Thibaut Barrre Sent: Monday, February 07, 2011 2:08 PM To: removed\_email\_address@domain.invalid Subject: Re: [Ironruby-core] Preparing 1.1.2 release Hi Tomas, I’m willing to try 1.1.2 a bit on Mac OS X if you’d like. How can I download it ? (the link you provided is a .msi only if I’m right ?) As well, I recall someone mentioning issues to ensure RVM would be able to automatically download it (maybe EULA agreement on codeplex that could not be skipped). This would definitely help people on non Windows machine try it it, as RVM is pretty standard amongst rubyists these days (outside Windows I mean). Let me know if I can help! – Thibaut ---
**Author:** ![grujildo](https://www.ruby-forum.com/letter_avatar_proxy/v4/letter/g/94ad74/32.png) [@grujildo](https://www.ruby-forum.com/u/grujildo)\ **Post date:** [February 7, 2011, 11:55pm UTC](https://www.ruby-forum.com/t/preparing-1-1-2-release/202826/9 "2011-02-07T23:55:02Z")
> I’m cloning it right now (then I’ll look where is Ruby.sln, because I have > no idea yet :-)). I’ll report back here after doing a few basic tests. I can report the compile went without any issue as long as I’m on Mono 2.10 RC2. I was able to start “mono ir.exe” and do a couple of things. require “rubygems” raised a SIGSEGV: /tmp/mono-gdb-commands.2Rimy1:1: Error in sourced command file: unable to debug self # ================================================================= Got a SIGSEGV while executing native code. This usually indicates a fatal error in the mono runtime or one of the native libraries used by your application. Abort trap But well - it already compiles out of the box, which is good! – Thibaut ---
**Author:** ![grujildo](https://www.ruby-forum.com/letter_avatar_proxy/v4/letter/g/94ad74/32.png) [@grujildo](https://www.ruby-forum.com/u/grujildo)\ **Post date:** [February 8, 2011, 12:33am UTC](https://www.ruby-forum.com/t/preparing-1-1-2-release/202826/10 "2011-02-08T00:33:54Z")
> Great! I spent some time to make xbuild happy J, Im glad it works on > non-Windows boxes as well. Thanks for that really 🙂 I’ve got a question wrt the build script we could set up: are the resulting binaries different if I compile from Mac OS X, as compared with Ubuntu ? If they are identical, I could work on provisioning a Vagrant box with all that is required to generate the builds on Ubuntu automatically. This would let anyone with access to Vagrant (and I think it works on Windows too for the host) with the ability to automate the builds and tests for IronRuby on \*nix, and we could also push this to a VPS instance later on so that we keep fresh automated binaries for OS X / Ubuntu etc. Are the resulting binaries identical ? I filed a couple of Mono bugs (crashes) yesterday: > So this might be hitting one of them. Or another. I guess we can either > wait until these are fixed and try again or try to narrow the Rubygems crash > down to a simpler repro. I’ll wait a bit, given my current free time, but I will definitely try again later on (feel free to ping me if you want to try things out later on, by email or gtalk [removed\_email\_address@domain.invalid](mailto:removed_email_address@domain.invalid)). – Thibaut ---
**Author:** ![grujildo](https://www.ruby-forum.com/letter_avatar_proxy/v4/letter/g/94ad74/32.png) [@grujildo](https://www.ruby-forum.com/u/grujildo)\ **Post date:** [February 8, 2011, 12:26am UTC](https://www.ruby-forum.com/t/preparing-1-1-2-release/202826/11 "2011-02-08T00:26:23Z")
Great! I spent some time to make xbuild happy :), I’m glad it works on non-Windows boxes as well. I filed a couple of Mono bugs (crashes) yesterday: [http://bugzilla.novell.com/show\_bug.cgi?id=669808](http://bugzilla.novell.com/show_bug.cgi?id=669808)[https://bugzilla.novell.com/show\_bug.cgi?id=669808](https://bugzilla.novell.com/show_bug.cgi?id=669808) (GetCustomAttributes crash) [http://bugzilla.novell.com/show\_bug.cgi?id=669815](http://bugzilla.novell.com/show_bug.cgi?id=669815) (non-deterministic crash in /nointerpret) So this might be hitting one of them. Or another. I guess we can either wait until these are fixed and try again or try to narrow the Rubygems crash down to a simpler repro. Tomas From: [removed\_email\_address@domain.invalid](mailto:removed_email_address@domain.invalid) [[mailto:removed\_email\_address@domain.invalid](mailto:removed_email_address@domain.invalid)] On Behalf Of Thibaut Barrre Sent: Monday, February 07, 2011 2:54 PM To: [removed\_email\_address@domain.invalid](mailto:removed_email_address@domain.invalid) Subject: Re: [Ironruby-core] Preparing 1.1.2 release I’m cloning it right now (then I’ll look where is Ruby.sln, because I have no idea yet :-)). I’ll report back here after doing a few basic tests. I can report the compile went without any issue as long as I’m on Mono 2.10 RC2. I was able to start “mono ir.exe” and do a couple of things. require “rubygems” raised a SIGSEGV: /tmp/mono-gdb-commands.2Rimy1:1: Error in sourced command file: unable to debug self # ================================================================= Got a SIGSEGV while executing native code. This usually indicates a fatal error in the mono runtime or one of the native libraries used by your application. Abort trap But well - it already compiles out of the box, which is good! – Thibaut ---
**Author:** ![grujildo](https://www.ruby-forum.com/letter_avatar_proxy/v4/letter/g/94ad74/32.png) [@grujildo](https://www.ruby-forum.com/u/grujildo)\ **Post date:** [February 8, 2011, 7:16am UTC](https://www.ruby-forum.com/t/preparing-1-1-2-release/202826/12 "2011-02-08T07:16:31Z")
Re binaries - 3 flavors are currently built: 1. ``` Desktop CLR 4.0 (.NET FW 4.0, Mono 2.10) ``` 2. ``` Core CLR 4.0 (Silverlight 4.0, Moonlight) ``` 3. ``` Core CLR 3.0 (Windows Phone 7) ``` So yes, the binaries should be equivalent. They won’t be byte-for-byte equal, but should functionally be the same. So should be binaries built on Windows using Microsoft C# compiler or Mono C# compiler. Re packaging and build automation: Sync with Jeff H. who maintains IronPython. We should have one solution for both languages. Tomas From: removed\_email\_address@domain.invalid [[mailto:removed\_email\_address@domain.invalid](mailto:removed_email_address@domain.invalid)] On Behalf Of Thibaut Barrre Sent: Monday, February 07, 2011 3:33 PM To: removed\_email\_address@domain.invalid Subject: Re: [Ironruby-core] Preparing 1.1.2 release Great! I spent some time to make xbuild happy :), I’m glad it works on non-Windows boxes as well. Thanks for that really 🙂 I’ve got a question wrt the build script we could set up: are the resulting binaries different if I compile from Mac OS X, as compared with Ubuntu ? If they are identical, I could work on provisioning a Vagrant box with all that is required to generate the builds on Ubuntu automatically. This would let anyone with access to Vagrant (and I think it works on Windows too for the host) with the ability to automate the builds and tests for IronRuby on \*nix, and we could also push this to a VPS instance later on so that we keep fresh automated binaries for OS X / Ubuntu etc. Are the resulting binaries identical ? I filed a couple of Mono bugs (crashes) yesterday: So this might be hitting one of them. Or another. I guess we can either wait until these are fixed and try again or try to narrow the Rubygems crash down to a simpler repro. I’ll wait a bit, given my current free time, but I will definitely try again later on (feel free to ping me if you want to try things out later on, by email or gtalk removed\_email\_address@domain.invalid[mailto:removed\_email\_address@domain.invalid](mailto:removed_email_address@domain.invalid)). – Thibaut