# Heads Up: RubyGems.org and universal-dotnet **URL:** \ **Category:** IronRuby\ **Created:** [May 25, 2010, 9:06am UTC](https://www.ruby-forum.com/t/heads-up-rubygems-org-and-universal-dotnet/189136 "2010-05-25T09:06:15Z")\ **Posts on this page:** 4\ **Page:** 1
**Author:** ![hotgazpacho](https://www.ruby-forum.com/letter_avatar_proxy/v4/letter/h/a587f6/32.png) [@hotgazpacho](https://www.ruby-forum.com/u/hotgazpacho)\ **Post date:** [May 25, 2010, 9:06am UTC](https://www.ruby-forum.com/t/heads-up-rubygems-org-and-universal-dotnet/189136/1 "2010-05-25T09:06:15Z")
Just a heads up: If you do manage to upgrade your Ruby Gems version to 1.3.7 (as I demonstrate here: [http://hotgazpacho.org/2010/05/ironruby-gem-update-system/](http://hotgazpacho.org/2010/05/ironruby-gem-update-system/)), you will not be able to install gems that have a platform of universal-dotnet. It appears that this is because: 1. RubyGems 1.3.7 includes my patch for IronRuby platform (universal-dotnet) 2. [RubyGems.org](http://RubyGems.org) have not updated to 1.3.7, and appear to be marshaling the platform over the wire as universal-unknown (and of course, universal-dotnet != universal-unknown) If you want to use bundler, however, you can upgrade to 1.3.6, as both ends treat universal-dotnet as universal-unknown. ---
**Author:** ![hotgazpacho](https://www.ruby-forum.com/letter_avatar_proxy/v4/letter/h/a587f6/32.png) [@hotgazpacho](https://www.ruby-forum.com/u/hotgazpacho)\ **Post date:** [May 25, 2010, 5:08pm UTC](https://www.ruby-forum.com/t/heads-up-rubygems-org-and-universal-dotnet/189136/2 "2010-05-25T17:08:38Z")
That’s pretty bad! So basically all IronRuby gems won’t be installable on RubyGems 1.3.7. Sounds like this will be fixed when [RubyGems.org](http://RubyGems.org)[http://RubyGems.org](http://RubyGems.org) updates to it? In the meantime is there a downside to suggesting no one upgrade until [RubyGems.org](http://RubyGems.org)[http://RubyGems.org](http://RubyGems.org) does? ~Jimmy On May 25, 2010, at 3:06 AM, “Will G.” \ wrote: Just a heads up: If you do manage to upgrade your Ruby Gems version to 1.3.7 (as I demonstrate here: [http://hotgazpacho.org/2010/05/ironruby-gem-update-system/](http://hotgazpacho.org/2010/05/ironruby-gem-update-system/) [http://hotgazpacho.org/2010/05/ironruby-gem-update-system/](http://hotgazpacho.org/2010/05/ironruby-gem-update-system/)), you will not be able to install gems that have a platform of universal-dotnet. It appears that this is because: 1. RubyGems 1.3.7 includes my patch for IronRuby platform (universal-dotnet) 2. [RubyGems.org](http://RubyGems.org)[http://RubyGems.org](http://RubyGems.org) have not updated to 1.3.7, and appear to be marshaling the platform over the wire as universal-unknown (and of course, universal-dotnet != universal-unknown) If you want to use bundler, however, you can upgrade to 1.3.6, as both ends treat universal-dotnet as universal-unknown. – Will G. [http://hotgazpacho.org/](http://hotgazpacho.org/)[http://hotgazpacho.org/](http://hotgazpacho.org/) * * * Ironruby-core mailing list removed\_email\_address@domain.invalid[mailto:removed\_email\_address@domain.invalid](mailto:removed_email_address@domain.invalid) [http://rubyforge.org/mailman/listinfo/ironruby-core](http://rubyforge.org/mailman/listinfo/ironruby-core) ---
**Author:** ![hotgazpacho](https://www.ruby-forum.com/letter_avatar_proxy/v4/letter/h/a587f6/32.png) [@hotgazpacho](https://www.ruby-forum.com/u/hotgazpacho)\ **Post date:** [May 25, 2010, 5:12pm UTC](https://www.ruby-forum.com/t/heads-up-rubygems-org-and-universal-dotnet/189136/3 "2010-05-25T17:12:09Z")
On May 25, 2010, at 11:08 AM, “Jimmy S.” \ wrote: That’s pretty bad! So basically all IronRuby gems won’t be installable on RubyGems 1.3.7. Correction … IronRuby gems won’t be installable if you upgrade to RubyGems 1.3.7 before [RubyGems.org](http://RubyGems.org)[http://RubyGems.org](http://RubyGems.org) upgrades, right? Sounds like this will be fixed when [http://RubyGems.org](http://RubyGems.org) [RubyGems.org](http://RubyGems.org)[http://RubyGems.org](http://RubyGems.org) updates to it? In the meantime is there a downside to suggesting no one upgrade until [http://RubyGems.org](http://RubyGems.org) [RubyGems.org](http://RubyGems.org)[http://RubyGems.org](http://RubyGems.org) does? ~Jimmy On May 25, 2010, at 3:06 AM, “Will G.” \<[mailto:removed\_email\_address@domain.invalid](mailto:removed_email_address@domain.invalid)removed\_email\_address@domain.invalid[mailto:removed\_email\_address@domain.invalid](mailto:removed_email_address@domain.invalid)\> wrote: Just a heads up: If you do manage to upgrade your Ruby Gems version to 1.3.7 (as I demonstrate here: [http://hotgazpacho.org/2010/05/ironruby-gem-update-system/](http://hotgazpacho.org/2010/05/ironruby-gem-update-system/) [http://hotgazpacho.org/2010/05/ironruby-gem-update-system/](http://hotgazpacho.org/2010/05/ironruby-gem-update-system/) [http://hotgazpacho.org/2010/05/ironruby-gem-update-system/](http://hotgazpacho.org/2010/05/ironruby-gem-update-system/)), you will not be able to install gems that have a platform of universal-dotnet. It appears that this is because: 1. RubyGems 1.3.7 includes my patch for IronRuby platform (universal-dotnet) 2. [http://RubyGems.org](http://RubyGems.org) [RubyGems.org](http://RubyGems.org)[http://RubyGems.org](http://RubyGems.org) have not updated to 1.3.7, and appear to be marshaling the platform over the wire as universal-unknown (and of course, universal-dotnet != universal-unknown) If you want to use bundler, however, you can upgrade to 1.3.6, as both ends treat universal-dotnet as universal-unknown. – Will G. [http://hotgazpacho.org/](http://hotgazpacho.org/)[http://hotgazpacho.org/](http://hotgazpacho.org/)[http://hotgazpacho.org/](http://hotgazpacho.org/) * * * Ironruby-core mailing list [mailto:removed\_email\_address@domain.invalid](mailto:removed_email_address@domain.invalid)removed\_email\_address@domain.invalid[mailto:removed\_email\_address@domain.invalid](mailto:removed_email_address@domain.invalid) [http://rubyforge.org/mailman/listinfo/ironruby-core](http://rubyforge.org/mailman/listinfo/ironruby-core)[http://rubyforge.org/mailman/listinfo/ironruby-core](http://rubyforge.org/mailman/listinfo/ironruby-core) * * * Ironruby-core mailing list removed\_email\_address@domain.invalid[mailto:removed\_email\_address@domain.invalid](mailto:removed_email_address@domain.invalid) [http://rubyforge.org/mailman/listinfo/ironruby-core](http://rubyforge.org/mailman/listinfo/ironruby-core) ---
**Author:** ![hotgazpacho](https://www.ruby-forum.com/letter_avatar_proxy/v4/letter/h/a587f6/32.png) [@hotgazpacho](https://www.ruby-forum.com/u/hotgazpacho)\ **Post date:** [May 25, 2010, 5:56pm UTC](https://www.ruby-forum.com/t/heads-up-rubygems-org-and-universal-dotnet/189136/4 "2010-05-25T17:56:04Z")
That is the way I understand it, yes. I may be wrong, but this is the conclusion I came to poking around a bit in RubyGems last night. In the mean time, putting this file: [http://github.com/hotgazpacho/ironruby/blob/gem-update-fix/Merlin/External.LCA\_RESTRICTED/Languages/Ruby/redist-libs/ruby/site\_ruby/1.8/rubygems/defaults/ironruby.rb](http://github.com/hotgazpacho/ironruby/blob/gem-update-fix/Merlin/External.LCA_RESTRICTED/Languages/Ruby/redist-libs/ruby/site_ruby/1.8/rubygems/defaults/ironruby.rb) [http://github.com/hotgazpacho/ironruby/blob/gem-update-fix/Merlin/External.LCA\_RESTRICTED/Languages/Ruby/redist-libs/ruby/site\_ruby/1.8/rubygems/defaults/ironruby.rb](http://github.com/hotgazpacho/ironruby/blob/gem-update-fix/Merlin/External.LCA_RESTRICTED/Languages/Ruby/redist-libs/ruby/site_ruby/1.8/rubygems/defaults/ironruby.rb)in IronRuby\lib\ruby\site\_ruby\1.8\rubygems\defaults directory will allow you to install gems whose platform is not marshaled correctly. – Will G. [http://hotgazpacho.org/](http://hotgazpacho.org/) On Tue, May 25, 2010 at 11:09 AM, Jimmy S. \<