Bundle install error: Source does not contain any versions of

Question

My gem file contains:

gem "breadcrumb", :git => "git@github.com:mjacobus/Breadcrumb.git"

gem "simple_menu", :git => "git@github.com:mjacobus/simple_menu.git"

The first gem installs as expected, but the second one fails.

Updating git@github.com:mjacobus/simple_menu.git
Fetching gem metadata from https://rubygems.org/........
Could not find gem 'simple_menu (>= 0) ruby' in git@github.com:mjacobus/simple_menu.git (at master).
Source does not contain any versions of 'simple_menu (>= 0) ruby'

Similar posts points to the lack of the .gemspec file, but this file exists. https://github.com/mjacobus/simple_menu/blob/master/simple_menu.gemspec

I am probably doing something stupid that someone else's eyes will be able to see.

edit

I cloned the repo into the vendor/plugins folder and changed my Gemfile

gem "simple_menu", :path => "vendor/plugins/simple_menu"

Bundle install issues now the error:

bundle install
Fetching gem metadata from https://rubygems.org/.......
Could not find gem 'simple_menu (>= 0) ruby' in source at vendor/plugins/simple_menu.
Source does not contain any versions of 'simple_menu (>= 0) ruby'

edit 2

I knew it was a stupid error. The gem name was not correct.

https://github.com/mjacobus/simple_menu/commit/1afca04b08a084dafb9bdf6e595a2bb9a7b7a55f

Would you please post your answer and mark it as the accepted answer? That will clear this question from the list of unanswered questions. Thanks! — Tass, Jul 08 '13 at 21:55
Thank you for the "edit 2" comment, made me double check and realized I did the same thing!! — Andrew Schwartz, Feb 29 '20 at 18:53
Note also that the name is case-sensitive, so `s.name = "Foo"` won't work with `gem "foo"`. — Drenmi, Jan 04 '21 at 09:17

d1jhoni1b · Answer 1 · 2016-01-19T21:27:24.113

As Marcelo mentioned, I got same error and it was a stupid thing:

gemspec file

Gem::Specification.new do |s|
 s.name = 'niche_wir_theme' 
 ....

Gem file (include)

gem 'niche-wir-theme', :git => 
....

As you can see in my gemspec i named using ("_") underscore and on my gemfile i was trying to call it with "-" (dash)...

(palmface) so just take care of the name notation, the one you are declaring at gemspec file against the one you use for the call in the gem file of the other project are probably different

score 10 · Answer 2 · answered Oct 16 '15 at 18:36

10

I ran into a similar problem with Rails 4.2. In my case it was another stupid mistake. It appears that if you leave "TODO" or "FIXME" in the comments in gemspec file, it will reject that gem and will throw the same error. Be sure to read the output of bundle command.

answered Oct 16 '15 at 18:36

Prakash Teli

1
1
2

Annoyingly I read this answer and still didn't notice the "TODO" warning which caused the error until I scrolled back up the bundler output. Thanks. – Kris Mar 29 '16 at 10:39

score 5 · Accepted Answer · edited May 05 '15 at 12:00

5

The gemspec file as named simplemenu.gemspec instead of simple_menu.gemspec.

edited May 05 '15 at 12:00

Arslan Ali

17,418
8
58
76

answered Jul 09 '13 at 23:37

Marcelo

1,702
2
24
42

Bundle install error: Source does not contain any versions of

edit

edit 2

3 Answers3

Linked