NameError: uninitialized constant Gem::SourceIndex

Question

This error appears for a new rails app, with nothing modified, when visiting the homepage (after successfully running bundle install).

Here are the version numbers:

ruby: 1.9.3p392 (2013-02-22 revision 39386) [x86_64-darwin12.2.1]

rails: 3.2.12

rvm: 1.18.14

gem: 2.0.0

bundler: 1.3.0.pre.8

Calling which ruby returns /Users/J/.rvm/rubies/ruby-1.9.3-p392/bin/ruby, which seems fishy, right?

Got the same error after upgrade from Ruby 1.9.3-p385 to 1.9.3-p392. Could it be a coincidence with some other change in my app? — Alex Kovshovik, Feb 25 '13 at 17:50
[This](http://stackoverflow.com/questions/15079182/cant-run-rails-server-after-accidentally-running-gem-update-system/15090490#15090490) seems related — Daniel Ristic, Mar 06 '13 at 10:05

Dogweather · Answer 1 · 2014-01-07T21:20:47.640

57

You need to update Bundler: gem update bundler

RubyGems release 2.0 seems to be the trigger for the error:

RubyGems 2.0 includes several new features and many breaking changes. Some of these changes will cause existing software to break. . . . If you are using bundler be sure to install a 1.3.0.prerelease version or newer. Older versions of bundler will not work with RubyGems 2.0.

Here are the issue details.

edited Jan 07 '14 at 21:20

answered Apr 10 '13 at 22:25

Dogweather

15,512
17
62
81

2

You should copy the actual text of the answer here so your answer doesn't become worthless due to a broken link in the future. – Carey Gregory Apr 10 '13 at 22:46
6

Its now Sep. 8th 2022 and this somehow still applies. Ruby is 3.1.2. Bundler is at 2.3.7 but the latest is 2.3.22. Rails is at 7.0.3.1 but when it does `bundle install` during a `rails new`, I get the same `uninitialized constant Gem::Source (NameError)` error. `gem update bundler` solved my issue. – pedz Sep 08 '22 at 22:23

score 29 · Answer 2 · answered May 13 '22 at 12:21

29

Thanks!

Rails-7, ruby 3.1.2, had the same issue

solved it by gem update --system

answered May 13 '22 at 12:21

chmich

834
9
20

1

this is the modern day real answer – ortonomy Jun 13 '22 at 11:42

score 18 · Answer 3 · answered Mar 30 '13 at 21:30

18

Run:

gem update --system 1.8.24

Sounds like there's something buggy with latest.

answered Mar 30 '13 at 21:30

Tylerc230

2,883
1
27
31

A colleague had updated to latest rubygems and was getting the same error as OP. I updated to latest to ensure that I got the same error. I did. I used the above answer to revert (to 1.8.25) and the error was resolved. – plasticide Apr 03 '13 at 17:14

score 15 · Answer 4 · answered Mar 15 '13 at 14:36

15

Have you tried updating your RubyGems?

gem update --system

answered Mar 15 '13 at 14:36

muttonlamb

6,341
3
26
35

2

same error and yes it says: Latest Version currently installed. Aborting. Still get error. – Codejoy Mar 28 '13 at 18:44

score 3 · Answer 5 · edited May 10 '13 at 03:13

3

gem update bundle && gem update --system

edited May 10 '13 at 03:13

Jared

25,627
7
56
61

answered May 10 '13 at 02:55

littleyang

41
2

Can you elaborate on how it will fix the issue? – Stuart M May 10 '13 at 03:14
in your project root directory,using the commands,remember to use "bundle install" – littleyang May 17 '13 at 07:56

score 0 · Answer 6 · answered May 24 '13 at 00:04

0

For me it was all of the above + using the new one on my nginx config.

answered May 24 '13 at 00:04

geermc4

578
6
18

NameError: uninitialized constant Gem::SourceIndex

6 Answers6

Linked