Need to fix several gems with invalid platfonm ("jruby" instead of "java")
Hi, I have a handful of gems that have jruby instead of java as the platform. This actually worked fine until recently so I didn't realize that I had made a mistake. Now bundler 1.1.1 complains that it can't bundle my project until those invalid gems have been yanked:
dw:jruby-1.6.7:(develop) pacer $ bundle
Fetching gem metadata from http://rubygems.org/.
Unfortunately, the gem pacer (0.8.5) has an invalid gemspec. As a result, Bundler cannot install this Gemfile. Please ask the gem author to yank the bad version to fix this issue. For more information, see http://bit.ly/syck-defaultkey.
The only problem that I can see with that gemspec is the invalid platform...
That's fine, but it seems that the gem yank command can not find gems that have an invalid platform.
dw::(master) pacer-neo4j $ gem yank pacer -v 0.8.5 -p jruby
Yanking gem from RubyGems.org...
Pushing gem to https://rubygems.org...
The version 0.8.5 does not exist.
If it's possible, I'd appreciate it if you could just correct the platform on each of them to "java". If that's not an option, then could you please yank them and let me know so that I can push corrected versions?
Thanks,
Darrick
Here is the list of effected gems that I know of:
pacer (0.9.1 jruby, 0.9.0 jruby, 0.8.6 jruby, 0.8.5 jruby, 0.8.1 jruby, 0.8.0 jruby, 0.7.1 jruby, 0.7.0 jruby)
pacer-dex (1.0.5 jruby, 1.0.3 jruby, 1.0.2 jruby, 1.0.1 jruby, 1.0.0 jruby)
pacer-neo4j (1.0.7 jruby, 1.0.6 jruby, 1.0.3 jruby, 1.0.2 jruby, 1.0.1 jruby, 1.0.0 jruby)
pacer-orient (1.0.4 jruby)
pacer-rexster (1.0.2 jruby, 1.0.0 jruby)
Support Staff 2 Posted by Nick Quaranto on 04 Aug, 2012 06:33 PM
Sorry, this comment was buried in our spam inbox.
I'd yank those gems and publish new ones. We can't modify existing gems. Check the FAQ here for more info:
http://help.rubygems.org/kb/gemcutter/removing-a-published-rubygem