Closed flyinprogrammer closed 11 years ago
So v1.8.25 of rubygems (for 1.9.3) is here: https://github.com/rubygems/rubygems/blob/v1.8.25/lib/rubygems/dependency.rb#L35
And v2.0.3 of rubygems (for 2.0.0) is here: https://github.com/rubygems/rubygems/blob/v2.0.3/lib/rubygems/dependency.rb#L38
But what's weird is that, the rubygems 2.0.3 dependency code hasn't changed in 5 months, and the combination of the 2.0.3 + 2.0.0-p195 was working up until yesterday; so my first guess that the marshaling was somehow broken between 1.9.3 and 2.0.0 cannot be true. So, we are going to try and find what version of the plugin we were running prior to yesterday so we can do a diff to find the defect -- mr. rhodes is on it.
https://github.com/sonatype/nexus-ruby-support/commit/e141922023bdf26fcb23b07926dd927e97adfe06
This has to be the commit; because it's the only thing that would have an impact... because it's really the only thing that has changed. I have meetings and what not this morning; i'll work with tyler to get my machine configured to dev on; and then i'll trace this down.
could please give me you Gemfile which you used to produce that error ?
http://puu.sh/33Jz0/4c068450e4.png
hasn't changed in 3 weeks.
thanx for the Gemfile. the following gist (hopefully) shows the problematic gem: https://gist.github.com/mkristian/5677789
so the memcache-client-1.6.3.gem has a dependency to '["RubyLine"]' the [" and "] are part of that gemname. and that gemname looks causes the problem with newer ruby/rubygems/bundler versions. looking at https://rubygems.org/gems/memcache-client/versions/1.6.3 the name is displayed in a correct form. so the fix I am going to implement is fix the name in a similar manner as the website is doing.
please reopen the issue if it remains a problem. on my side the offending ["RubyLine"] is gone.
perfect - I'll test this as soon as I can
this is definitely fixed! thank you so much!
This only exists with: ruby-2.0.0-p195 Rubygems 2.0.3 (3 months ago) Bundler 1.35 (release date: April 4, 2013)
This just popped up yesterday when we built and installed the latest nexus-ruby-plugin. Prior to that 2.0.0 was working. So I'm officially confused.