How to handle deprecated gem warning (SourceIndex#all_gems)? [duplicate]

Answer 1

It was called from the Bundler gem. Try updating bundler to see if it helps

sudo gem update bundler

Answer 2

The Pry gem uses the rubygems API directly and can't be fixed by just running gem pristine --all unfortunately.

I forked the Pry gem and added fixes using non-deprecated API calls. Pending a merge to master, here is the fork: https://github.com/dvdplm/pry

Answer 3

Qoute:

As far as I see from the sources:
Simply patch rubygems_integration.rb, line 256:
- Gem.source_index.all_gems.values
+ Gem.source_index.gems.values
Reason:
Gem::SourceIndex#all_gems was just returning @gems, and now there is an attr_reader for @gems. I think that was the reason to remove the all_gems method.

Source: ruby-forum.com

Answer 4

I deleted and reinstalled ruby 1.9.2 via RVM and then uninstalled all gems:

gem list --no-versions

Put the result in a file called gems (cut out the error messages). Then do:

GEMS=`cat gems`
for x in $GEMS ; do gem uninstall $x -aIx; done

After that I was able to run the pristine command suggested by others:

gem pristine --all --no-extensions

That's when the errors disappeared.

Answer 5

I updated bundler ('gem update bundler') from 1.0.12 to 1.0.15. Now all is well.

Answer 6

I got the same errors for a bunch of my gems in a non-Rails environment when I upgraded to rubygems 1.8.0. I got the warnings any time rubygems is required. Looking around the 'Net, it seems like it might be a problem also with rubygems 1.7.x, but I never had one of those versions installed so I'm not sure. I fixed this by running:

gem pristine --all --no-extensions

I had to run it a few times - it kept erroring out (but usually not in the same place from run to run). Eventually it got far enough that it had addressed the majority of my gems.

There were a few gems that didn't get their specifications regenerated correctly (json and sequel, specifically in my case) because they needed to build an extension. (The gem command output indicated it was skipping them, though it was easy to miss that message amidst all the deprecation warnings.) For those gems, I uninstalled them and then reinstalled them again (they'd previously been installed by bundler in rubygems 1.5.x) and that fixed the remaining warnings. It may be that I could have started with that plan of attack originally, but I didn't try.