Sign Up

Sign Up to our social questions and Answers Engine to ask questions, answer people’s questions, and connect with other people.

Have an account? Sign In

Have an account? Sign In Now

Sign In

Login to our social questions & Answers Engine to ask questions answer people’s questions & connect with other people.

Sign Up Here

Forgot Password?

Don't have account, Sign Up Here

Forgot Password

Lost your password? Please enter your email address. You will receive a link and will create a new password via email.

Have an account? Sign In Now

You must login to ask a question.

Forgot Password?

Need An Account, Sign Up Here

Please briefly explain why you feel this question should be reported.

Please briefly explain why you feel this answer should be reported.

Please briefly explain why you feel this user should be reported.

Sign InSign Up

The Archive Base

The Archive Base Logo The Archive Base Logo

The Archive Base Navigation

  • SEARCH
  • Home
  • About Us
  • Blog
  • Contact Us
Search
Ask A Question

Mobile menu

Close
Ask a Question
  • Home
  • Add group
  • Groups page
  • Feed
  • User Profile
  • Communities
  • Questions
    • New Questions
    • Trending Questions
    • Must read Questions
    • Hot Questions
  • Polls
  • Tags
  • Badges
  • Buy Points
  • Users
  • Help
  • Buy Theme
  • SEARCH
Home/ Questions/Q 5942477
In Process

The Archive Base Latest Questions

Editorial Team
  • 0
Editorial Team
Asked: May 22, 20262026-05-22T16:15:31+00:00 2026-05-22T16:15:31+00:00

OK, so i updated to gem version 1.8.1 and got this problem where it

  • 0

OK, so i updated to gem version 1.8.1 and got this problem where it would have too many deprecation warnings so i rolled back to version 1.7.2 and also ran gem pristine --all --no-extensions following what rubyonrails error when update to gem 1.8.1, said to do, but now i still have the some warnings here and there(rake commands and some gems).

I ran rake db:migrate and i get this:

NOTE: Gem::SourceIndex#all_gems is deprecated with no replacement. It will be removed on or after 2011-10-01.
Gem::SourceIndex#all_gems called from c:/Ruby192/lib/ruby/gems/1.9.1/gems/bundler-1.0.13/lib/bundler/rubygems_
integration.rb:256

I tried running gem pristine --all --no-extensions again but it gives me invalid option: –no-extensions

Any ideas how to get rid of this little nuisance?

Thanks.

  • 1 1 Answer
  • 0 Views
  • 0 Followers
  • 0
Share
  • Facebook
  • Report

Leave an answer
Cancel reply

You must login to add an answer.

Forgot Password?

Need An Account, Sign Up Here

1 Answer

  • Voted
  • Oldest
  • Recent
  • Random
  1. Editorial Team
    Editorial Team
    2026-05-22T16:15:32+00:00Added an answer on May 22, 2026 at 4:15 pm

    Bundler 1.0.13 (version released May 4, 2011) running with rubygems 1.7.2 issues this annoying deprecation warning:

    NOTE: Gem::SourceIndex#all_gems is deprecated with no replacement. It will be removed on or after 2011-10-01.
    Gem::SourceIndex#all_gems called from /Users/me/.rvm/gems/ruby-1.9.2-p180@composer/gems/bundler-1.0.13/lib/bundler/rubygems_integration.rb:256

    A fix was committed on 5/11/2011 in the Bundler repo to correct an issue submitted 5/6/2011.

    Pending release of Bundler 1.1, you can try this solution:

    $ gem uninstall bundler

    $ gem install bundler –version=1.0.12

    I hope this helps. Took some digging to find it.

    • 0
    • Reply
    • Share
      Share
      • Share on Facebook
      • Share on Twitter
      • Share on LinkedIn
      • Share on WhatsApp
      • Report

Sidebar

Related Questions

I have installed bootstrap to my Rails 3.2 app this way (through Gemfile): gem
I've got this problem that It always hit the PropertyAccessException when trying to saveOrUpdate();
This question is an expanded version of Facebook Real-time updated does not call our
I have a private git server hosting a gem we developed. The gem got
For example I have this gem called Authlogic-openid, that plugin is outdated, no longer
Update: Check out this follow-up question: Gem Update on Windows - is it broken?
Updated question, see below I'm starting a new project and I would like to
----------Updated ------------ codymanix and moonshadow have been a big help thus far. I was
So... I've got a migration (post.rb uses the state_machine gem) class AddVerifiedAtToPost < ActiveRecord::Migration
This hasn't got anything to do with paperclip, btw. I've upgraded to rails 3.2

Explore

  • Home
  • Add group
  • Groups page
  • Communities
  • Questions
    • New Questions
    • Trending Questions
    • Must read Questions
    • Hot Questions
  • Polls
  • Tags
  • Badges
  • Users
  • Help
  • SEARCH

Footer

© 2021 The Archive Base. All Rights Reserved
With Love by The Archive Base

Insert/edit link

Enter the destination URL

Or link to existing content

    No search term specified. Showing recent items. Search or use up and down arrow keys to select an item.