Psych-unfriendly env hates gem built in Psych-friendly env

[ruby]

Psych-unfriendly env hates gem built in Psych-friendly env

[tenderlove]

Hi David!

When you built the gem on 1.9.2, what version of rubygems were you using? (output of gem env)

[dchelimsky]

1.6.2. I tried it again locally after upgrading to 1.7.2 as well. Same result.

I should add that I used bundler's build task. Not sure what that would mean, since it shells out to 'gem build', but one never knows.

[dchelimsky]

On that last note, I will try building directly and see if I get the same result - but I won't be able to do this until tomorrow evening in all likelihood.

[dchelimsky]

Oh - and one last thing:

Hi Aaron!

[tenderlove]

Hi David!!

What commands did you use to build the gem? I can't seem to figure out the right command to do packaging via bundler.

Also, I tried building the gem on 1.9.2 like this:

$ gem build rspec-mocks.gemspec

The resulting gem installed fine on 1.9.2 and 1.8.7. Did you have to upload your gem to rubygems.org before it would break?

[dchelimsky]

Hi Aaron!!!

Bundler ships with some rake tasks that you can add to your Rake env like this:

Bundler::GemHelper.install_tasks

One of the tasks is 'build'

rake build

This shells out to "gem build": https://github.com/carlhuda/bundler/blob/1-0-stable/lib/bundler/gem_helper.rb#L40

I did have to upload my gem to rubygems.org before it would break. That makes this debugging effort extra special.

I fear I'm pointing you down a rabbit hole here. Let me figure out how to reproduce the problem, and then we can go from there. Good?

[tenderlove]

Hi David!!!! ❤️

Sounds good. Let me know what you find!

[dchelimsky]

I am unable to reproduce this locally. It must have never happened and I must have been on crack. Closing this until the next time I'm on crack, only next time I'll take better notes.

[tenderlove]

Hah! Okay. Let me know if you encounter this again!

[dchelimsky]

Hey - guess what? I'm an idiot, and my idiocy has made it so you can see what's actually happening here. I pushed rspec-2.6.0.rc3, which I built with rubygems-1.6.2 in ruby-1.9.2-p180 (rvm). Try "gem install rspec -v 2.6.0.rc3" and you'll see the error this issue.

I will now release 2.6.0.rc4, built on 1.8.7 :)

[dchelimsky]

FYI: rspec/rspec-core#358, rspec/rspec-dev#17

[dchelimsky]

Oh, and https://rubygems.org/gems/rspec/versions/2.6.0.rc3.

[dchelimsky]

OK - I now have steps to reproduce.

• Go to https://rubygems.org/gems/rspec/versions/2.6.0.rc1 and download the gem
• In a ruby-1.9.2 env, run gem spec rspec-2.6.0.rc1 and you'll see gem dependencies that look like this:

- !ruby/object:Gem::Dependency
  name: rspec-mocks
  requirement: &2152509300 !ruby/object:Gem::Requirement
    none: false
    requirements:
    - - =
      - !ruby/object:Gem::Version
        version: 2.6.0.rc4
  type: :runtime
  prerelease: false
  version_requirements: *2152509300

• Now switch to ruby 1.8.7 and run gem spec rspec-2.6.0.rc1 and you'll see gem dependencies that look like this:

- !ruby/object:Gem::Dependency 
  name: rspec-expectations
  prerelease: false
  requirement: &id002 !ruby/object:Gem::Requirement 
    none: false
    requirements: 
    - - !ruby/object:YAML::Syck::DefaultKey {}

      - !ruby/object:Gem::Version 
        hash: 15424061
        segments: 
        - 2
        - 6
        - 0
        - rc
        - 4
        version: 2.6.0.rc4
  type: :runtime
  version_requirements: *id002

Same is true of rc3,which I am now going to yank.

If you want to really see this in action:

rvm 1.9.2@rspec-dev --create
git clone git://github.com/rspec/rspec-dev
cd rspec-dev
rake setup
# wait a while
rake gem:build
cd repos/rspec
rake clobber
rake build
gem spec pkg/rspec-2.6.0.rc4 # assuming you do this before the next release
rvm 1.8.7@rspec-dev --create
bundle install
gem spec pkg/rspec-2.6.0.rc4

[myronmarston]

Given the fact that psych is included (but not compiled into) ruby 1.9, I imagine it would be hard to ship a fix for 1.9.2 for this. And given the fact that pysch and syck have known differences, I'm not entirely sure what the solution will be.

Instead, I'm wondering if gemcutter should reject any gems that have a YAML gemspec file that is unparseable by Syck. It could be part of what runs on gem push my_gem.

[dchelimsky]

Either what @myronmarston suggested or perhaps rubygems could warn when building a gem in an environment with Pysch compiled into it.

[dchelimsky]

This is reported to rubygems:

http://rubyforge.org/tracker/index.php?func=detail&aid=29163&group_id=126&atid=575