Invalid gemspec warnings

[tdreyno]

I've been getting these warning on various rubies for the last few releases:

Installing aruba (0.4.10) Invalid gemspec in [/Users/tdreyno/.rbenv/versions/jruby-1.6.5/lib/ruby/gems/1.8/specifications/aruba-0.4.10.gemspec]: Illformed requirement ["#<YAML::Yecht::DefaultKey:0x5bdaaf56> 1.0.11"]

I had this issue on some of my own gems in the past, is it possible your packaging and releasing your gems with something other than Ruby 1.8.x? It seemed, at the time, that different rubies each made assumptions that weren't always compatible (well, it works, but not without warnings). So now I use only Ruby 1.8.7 for packaging.

[tdreyno]

Here's what the gemspec looks like BTW:

# -*- encoding: utf-8 -*-

Gem::Specification.new do |s|
  s.name = %q{aruba}
  s.version = "0.4.10"

  s.required_rubygems_version = Gem::Requirement.new(">= 0") if s.respond_to? :required_rubygems_version=
  s.authors = [%q{Aslak Hellesøy}, %q{David Chelimsky}, %q{Mike Sassak}, %q{Matt Wynne}]
  s.date = %q{2011-12-24}
  s.description = %q{CLI Steps for Cucumber, hand-crafted for you in Aruba}
  s.email = %q{[email protected]}
  s.homepage = %q{http://github.com/cucumber/aruba}
  s.rdoc_options = [%q{--charset=UTF-8}]
  s.require_paths = [%q{lib}]
  s.rubygems_version = %q{1.8.9}
  s.summary = %q{aruba-0.4.10}

  if s.respond_to? :specification_version then
    s.specification_version = 3

    if Gem::Version.new(Gem::VERSION) >= Gem::Version.new('1.2.0') then
      s.add_runtime_dependency(%q<cucumber>, [">= 1.1.1"])
      s.add_runtime_dependency(%q<childprocess>, [">= 0.2.3"])
      s.add_runtime_dependency(%q<ffi>, ["#<YAML::Yecht::DefaultKey:0x68b18cfb> 1.0.11"])
      s.add_runtime_dependency(%q<rspec>, [">= 2.7.0"])
      s.add_development_dependency(%q<bcat>, [">= 0.6.1"])
      s.add_development_dependency(%q<rdiscount>, [">= 1.6.8"])
      s.add_development_dependency(%q<rake>, [">= 0.9.2"])
    else
      s.add_dependency(%q<cucumber>, [">= 1.1.1"])
      s.add_dependency(%q<childprocess>, [">= 0.2.3"])
      s.add_dependency(%q<ffi>, ["#<YAML::Yecht::DefaultKey:0x68b18cfb> 1.0.11"])
      s.add_dependency(%q<rspec>, [">= 2.7.0"])
      s.add_dependency(%q<bcat>, [">= 0.6.1"])
      s.add_dependency(%q<rdiscount>, [">= 1.6.8"])
      s.add_dependency(%q<rake>, [">= 0.9.2"])
    end
  else
    s.add_dependency(%q<cucumber>, [">= 1.1.1"])
    s.add_dependency(%q<childprocess>, [">= 0.2.3"])
    s.add_dependency(%q<ffi>, ["#<YAML::Yecht::DefaultKey:0x68b18cfb> 1.0.11"])
    s.add_dependency(%q<rspec>, [">= 2.7.0"])
    s.add_dependency(%q<bcat>, [">= 0.6.1"])
    s.add_dependency(%q<rdiscount>, [">= 1.6.8"])
    s.add_dependency(%q<rake>, [">= 0.9.2"])
  end
end

[mattwynne]

Thanks for letting us know.

I've built the last few releases, and I probably did it using 1.9.3. Sorry, I hadn't realised it was causing a problem.

Is there anything else I can do, or do I just need to remember to switch to Ruby 1.8.7 to build the gem?

[tdreyno]

I think just switching to 1.8.7 is all. Something to do with the Yaml parser. Never truly understood myself.

There are some other bugs around if you google for "YAML::Yecht::DefaultKey", but they're not very informative. They just kind of stumble until rebuilding and pushing under 1.8

[mattwynne]

I've closed this, but it wouldn't hurt for someone other than me to test this and let me know if 0.4.11 is working any better.

[tdreyno]

Working for me.