-
-
Notifications
You must be signed in to change notification settings - Fork 2k
NoMethodError: undefined method remotes' for #<Bundler::Source::Gemspec:0x47101377289620 source at
.`> Did you mean? remote!
#6563
Comments
I'm not able to reproduce this issue. Can you please share the Bundler error template which will give me more information to better help you. |
This issue is caused when calling the The |
The error-message function did not provide an explicit source, and that could lead in some confusion especially with big Gemfiles. The command that is output, should be valid.
Thanks! I'm looking into this issue |
Is that something I omit in the Blunder response that you need? I update my answer but still see the status: user feedback required. Sorry, I may misinterpret the term "Bundler error template", I just started with ruby. |
…rect Check if source responds to `#remotes` before printing gem install error message ### What was the end-user problem that led to this PR? There is a bug that was introduced in #6211 that prints an error message during `bundle install` if a gem failed to be installed. The error message attempts to call the `#remotes` method on `Bundler::Source::Git` which it does not implement. ### What was your diagnosis of the problem? See #6563 ### What is your fix for the problem, implemented in this PR? Check if the `source` responds to `#remotes` before and return early ### Why did you choose this fix out of the possible options? This seems to be the most simplest fix without having to refactor a lot of code.
@colby-swandale I think we can close this with that PR merged? |
…rect Check if source responds to `#remotes` before printing gem install error message ### What was the end-user problem that led to this PR? There is a bug that was introduced in #6211 that prints an error message during `bundle install` if a gem failed to be installed. The error message attempts to call the `#remotes` method on `Bundler::Source::Git` which it does not implement. ### What was your diagnosis of the problem? See #6563 ### What is your fix for the problem, implemented in this PR? Check if the `source` responds to `#remotes` before and return early ### Why did you choose this fix out of the possible options? This seems to be the most simplest fix without having to refactor a lot of code. (cherry picked from commit f358c36)
what is the fix for this? |
I too would like to know the fix for this. I noticed that this only started happening for me after I updated bundler to Bundler version 2.1.0.pre.1 |
This issue was closed by a related PR. If you're having a similar issue on the latest bundler prerelease, could you please open a new issue with reproduction steps? Thanks! |
I am experiencing this problem when trying to run
bundler update
orbundler install
.My Bundler version is 1.16.2.
Backtrace
Environment
Bundler settings
Gemspec:
Gemfile
The text was updated successfully, but these errors were encountered: