Ironruby core - May 2010 - Heads Up: RubyGems.org and universal-dotnet

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/), 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 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 Green
http://hotgazpacho.org/
-------------- next part --------------
An HTML attachment was scrubbed...
URL:
<http://rubyforge.org/pipermail/ironruby-core/attachments/20100525/63b4b324/attachment.html>

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> updates to it? In the meantime is there
a downside to suggesting no one upgrade until
RubyGems.org<http://RubyGems.org> does?

~Jimmy

On May 25, 2010, at 3:06 AM, "Will Green" <will at
hotgazpacho.org<mailto:will at hotgazpacho.org>> 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/), 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.

--
Will Green
<http://hotgazpacho.org/>http://hotgazpacho.org/
_______________________________________________
Ironruby-core mailing list
Ironruby-core at rubyforge.org<mailto:Ironruby-core at rubyforge.org>
http://rubyforge.org/mailman/listinfo/ironruby-core
-------------- next part --------------
An HTML attachment was scrubbed...
URL:
<http://rubyforge.org/pipermail/ironruby-core/attachments/20100525/9dde5af4/attachment-0001.html>

On May 25, 2010, at 11:08 AM, "Jimmy Schementi" <Jimmy.Schementi at
microsoft.com<mailto:Jimmy.Schementi at microsoft.com>> 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> upgrades, right?

Sounds like this will be fixed when <http://RubyGems.org>
RubyGems.org<http://RubyGems.org> updates to it? In the meantime is there
a downside to suggesting no one upgrade until <http://RubyGems.org>
RubyGems.org<http://RubyGems.org> does?

~Jimmy

On May 25, 2010, at 3:06 AM, "Will Green" <<mailto:will at
hotgazpacho.org>will at hotgazpacho.org<mailto:will at
hotgazpacho.org>> 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/), 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> 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 Green
<http://hotgazpacho.org/><http://hotgazpacho.org/>http://hotgazpacho.org/
_______________________________________________
Ironruby-core mailing list
<mailto:Ironruby-core at rubyforge.org>Ironruby-core at
rubyforge.org<mailto:Ironruby-core at rubyforge.org>
<http://rubyforge.org/mailman/listinfo/ironruby-core>http://rubyforge.org/mailman/listinfo/ironruby-core
_______________________________________________
Ironruby-core mailing list
Ironruby-core at rubyforge.org<mailto:Ironruby-core at rubyforge.org>
http://rubyforge.org/mailman/listinfo/ironruby-core
-------------- next part --------------
An HTML attachment was scrubbed...
URL:
<http://rubyforge.org/pipermail/ironruby-core/attachments/20100525/47b732d0/attachment.html>

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>in
IronRuby\lib\ruby\site_ruby\1.8\rubygems\defaults directory will allow you
to install gems whose platform is not marshaled correctly.

--
Will Green
http://hotgazpacho.org/


On Tue, May 25, 2010 at 11:09 AM, Jimmy Schementi <
Jimmy.Schementi at microsoft.com> wrote:
> On May 25, 2010, at 11:08 AM, "Jimmy Schementi" <
> Jimmy.Schementi at microsoft.com> 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 upgrades, right?
>
> Sounds like this will be fixed when
<http://RubyGems.org>RubyGems.orgupdates to it? In the meantime is there a
downside to suggesting no one
> upgrade until <http://RubyGems.org>RubyGems.org does?
>
> ~Jimmy
>
> On May 25, 2010, at 3:06 AM, "Will Green" < <will at
hotgazpacho.org>
> will at hotgazpacho.org> 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/), 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>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 Green
> <http://hotgazpacho.org/>
<http://hotgazpacho.org/>http://hotgazpacho.org/
>
> _______________________________________________
> Ironruby-core mailing list
> <Ironruby-core at rubyforge.org>Ironruby-core at rubyforge.org
> <http://rubyforge.org/mailman/listinfo/ironruby-core>
> http://rubyforge.org/mailman/listinfo/ironruby-core
>
> _______________________________________________
> Ironruby-core mailing list
> Ironruby-core at rubyforge.org
> http://rubyforge.org/mailman/listinfo/ironruby-core
>
>
> _______________________________________________
> Ironruby-core mailing list
> Ironruby-core at rubyforge.org
> http://rubyforge.org/mailman/listinfo/ironruby-core
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL:
<http://rubyforge.org/pipermail/ironruby-core/attachments/20100525/6b301a31/attachment.html>