Bugs item #28906, was opened at 2011-02-03 15:42
You can respond by visiting:
http://rubyforge.org/tracker/?func=detail&atid=575&aid=28906&group_id=126
Category: `gem install` command
Group: None
Status: Open
Resolution: None
Priority: 3
Submitted By: Bernard Lambeau (blambeau)
Assigned to: Nobody (None)
Summary: Gems built with (rubygems 1.5.0 / ruby 1.9.2) do not install properly
with (1.5.0 / 1.8.7)
Initial Comment:
The build/install scenario below fails. It seems that the metadata generated by
1.9.2 is not properly loaded by 1.8.7. I've attached foo.gemspec.
blambeau@yemana foo % rvm use 1.9.2 && rm -rf pkg && gem build foo.gemspec
Successfully built RubyGem
Name: foo
Version: 1.0.0
File: foo-1.0.0.gem
blambeau@yemana foo % rvm use 1.8.7 && gem install foo-1.0.0.gem
ERROR: While executing gem ... (Gem::Exception)
ruby_code case not handled: YAML::PrivateType
I've made some investgations and here is what I've found:
* expection raise in ruby_code, which receives a YAML::PrivateType object
* called in Specification#to_ruby
* that the first entry that fails is autorequire: !!null
* I suspect !!null to behave differently in ruby 1.8.7 and 1.9.2, probably Syck
<> Psych
See also
http://help.rubygems.org/discussions/problems/483-gems-built-with-rubygems-150-ruby-192-do-not-install-properly-with-150-187
----------------------------------------------------------------------
You can respond by visiting:
http://rubyforge.org/tracker/?func=detail&atid=575&aid=28906&group_id=126
_______________________________________________
Rubygems-developers mailing list
http://rubyforge.org/projects/rubygems
Rubygems-developers@rubyforge.org
http://rubyforge.org/mailman/listinfo/rubygems-developers
