Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

"No url found for submodule path" #2243

Closed
matthew-dean opened this issue Feb 10, 2017 · 3 comments
Closed

"No url found for submodule path" #2243

matthew-dean opened this issue Feb 10, 2017 · 3 comments

Comments

@matthew-dean
Copy link

I'm getting this error when trying to pull via npm:

git submodule -q update --init --recursive: fatal: No url found for submodule path 'vendor/listen' in .gitmodules

Any reason why installing the submodule should fail?

@nex3
Copy link
Contributor

nex3 commented Feb 10, 2017

I'm guessing you're on the next or master branch, which no longer includes that submodule. You shouldn't need to run git submodule anymore, and you can delete vendor/listen if you'd like.

@nex3 nex3 closed this as completed Feb 10, 2017
@hwhelchel
Copy link

hwhelchel commented Apr 15, 2017

Hi @nex3 I'm experience this issue as well on the dynamic_includes branch and using bundler.

Gemfile snippet

source 'https://rubygems.org'

git_source(:github) do |repo_name|
  repo_name = "#{repo_name}/#{repo_name}" unless repo_name.include?("/")
  "https://github.com/#{repo_name}.git"
end

ruby '2.4.1'
# Bundle edge Rails instead: gem 'rails', github: 'rails/rails'
gem 'rails', '~> 5.0.2'
# Use postgresql as the database for Active Record
gem 'pg', '~> 0.15'
# Use SCSS for stylesheets
gem 'sass', github: 'sass/sass', branch: 'dynamic_includes'
gem 'sass-rails', '~> 5.0.5'

# ...
Fetching https://github.com/sass/sass.git
fatal: no submodule mapping found in .gitmodules for path 'vendor/listen'

Retrying `git submodule deinit --all` due to error (2/4): Bundler::Source::Git::GitCommandError Git error: command `git submodule deinit --all` in directory /Users/harry/.rbenv/versions/2.4.1/lib/ruby/gems/2.4.0/bundler/gems/sass-c3a38aaccaea has failed.
If this error persists you could try removing the cache directory '/Users/harry/.rbenv/versions/2.4.1/lib/ruby/gems/2.4.0/cache/bundler/git/sass-f93669b09c0ed3df285fed8ee8f7fafb2f69833f'fatal: no submodule mapping found in .gitmodules for path 'vendor/listen'

Retrying `git submodule deinit --all` due to error (3/4): Bundler::Source::Git::GitCommandError Git error: command `git submodule deinit --all` in directory /Users/harry/.rbenv/versions/2.4.1/lib/ruby/gems/2.4.0/bundler/gems/sass-c3a38aaccaea has failed.
If this error persists you could try removing the cache directory '/Users/harry/.rbenv/versions/2.4.1/lib/ruby/gems/2.4.0/cache/bundler/git/sass-f93669b09c0ed3df285fed8ee8f7fafb2f69833f'fatal: no submodule mapping found in .gitmodules for path 'vendor/listen'

Retrying `git submodule deinit --all` due to error (4/4): Bundler::Source::Git::GitCommandError Git error: command `git submodule deinit --all` in directory /Users/harry/.rbenv/versions/2.4.1/lib/ruby/gems/2.4.0/bundler/gems/sass-c3a38aaccaea has failed.
If this error persists you could try removing the cache directory '/Users/harry/.rbenv/versions/2.4.1/lib/ruby/gems/2.4.0/cache/bundler/git/sass-f93669b09c0ed3df285fed8ee8f7fafb2f69833f'fatal: no submodule mapping found in .gitmodules for path 'vendor/listen'

Git error: command `git submodule deinit --all` in directory /Users/harry/.rbenv/versions/2.4.1/lib/ruby/gems/2.4.0/bundler/gems/sass-c3a38aaccaea has failed.
If this error persists you could try removing the cache directory
'/Users/harry/.rbenv/versions/2.4.1/lib/ruby/gems/2.4.0/cache/bundler/git/sass-f93669b09c0ed3df285fed8ee8f7fafb2f69833f'

I first tried removing the cache directory as git advises which did not work.

I forked sass/sass and added back the .gitmodules file and was able to successfully bundle.

Is there a better solution that I am missing?

@nex3
Copy link
Contributor

nex3 commented May 18, 2017

Running from branches other than stable, next, and master is not something we really support.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
3 participants