Skip to content

HTTPS clone URL

Subversion checkout URL

You can clone with HTTPS or Subversion.

Download ZIP

Loading…

No such file or directory -- .../gems/rspec-core-2.7.0/bin/rspec (LoadError) #478

Closed
fabianoalmeida opened this Issue · 4 comments

2 participants

@fabianoalmeida

Hi rspec group!

I saw this error happen when I run autotest -n (and ruby version 1.9.2-p180) on terminal and after that it's showing me all my specs and this error message.

I went to the folder rspec-core-2.7.0 and I can't see any folder called bin. So, I suppose that exist a problem in the .gemspec inside the project.

When I saw the .gemspec file, I didn't see any reference to bin folder. But here I can see the new bindir, however it's looking for a folder called bin.

I need execute some command, run something? Before this gem update, I was using 2.6.4 version and all of my specs were working fine.

I'm using this gems cause this help to identify this problem.

Thanks for your help.

@dchelimsky
Owner

@faianoalmeida - thanks for the report. I see what the problem is - I moved the bindir to exe so we could bundle install --binstubs into bin for local development. When I do that, it puts the rspec command in bin, so I would never have seen this bug in action :(

Fix coming soon.

@fabianoalmeida

@dchelimsky - thank you for the quick reply. And about your self-punishment (lol), this happens, right?

I have a question in your reply... Where can I execute this command (bundle install --bunstubs)? Whether I understood, I could this commend inside the bin folder in .../gems/rspec-core-2.7.0/, that's correct?

Cause this answer is "yes", I need a Gemfile file to execute this command. How can you see, I don't understand where I could execute this command.

Thanks one more time.

Regards.

@dchelimsky
Owner

@fabianoalmeida - bunstubs are in a completely different industry :) It's binstubs. When you run bundle install --binstubs in the project root directory, it creates a bin folder and puts stub executables for any gems that ship with executables. This helps to avoid version conflicts (i.e. if you have both rake 0.8.7 and 0.9.2 installed, but this project needs 0.8.7).

If you're looking for a workaround until this is released, the best bet is to rewrite the SPEC_PROGRAM variable so it looks like https://github.com/rspec/rspec-core/blob/96fa1191fcbd707fc27522fe74f1103626d103b7/lib/autotest/rspec2.rb#L8.

HTH,
David

@fabianoalmeida

@dchelimsky - thank you so much!

I never create a gem, so you help me and I learned a bit more about it. I'll describe what I did to solve this "bug", right?

I ran bundle install --binstubs and after that was created a bin folder on the root application folder.

After that, I tryed to run autotest -n and was necessary to install all missed gems. So, bundle install. That's created a folder called rspec-code.

The last step => I copied the bin folder to rspec-code/ruby/1.9.1/gems/rspec-core-2.7.0/.

Done! I ran autotest -n and all worked fine.

I hope that could help anyone with the same problem.

@sj26 sj26 referenced this issue from a commit in sj26/rspec-core
@dchelimsky dchelimsky tell autotest the correct place to find the rspec command
- Fixes #478.
fc70352
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Something went wrong with that request. Please try again.