-
-
Notifications
You must be signed in to change notification settings - Fork 242
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
nanoc command (rvm) fails to launch with error: `default_gemfile': Could not locate Gemfile (Bundler::GemfileNotFound) #447
Comments
Hi, thanks for reporting!
|
You can temporarily use 3.6.11, or, even better, use a Gemfile! |
Yeah, @ddfreyne I can confirm that throwing in a Gemfile with nanoc in it worked. Thanks for getting me over the hump and please let me know when I can test the new version and get this issue closed. I really appreciate the fast response! 👍 |
This is fixed by #449. The 3.7.1 release will follow shortly. |
3.7.1 is released. |
I am still having the problem. Haven't narrowed down yet what's going on. |
@pitosalas Is the issue you’re experiencing #452, rather than this one? |
I uninstalled my ruby and gems (in desperation) and downgraded to Nanoc 3.6.9 to make the problem go away. With 3.6.9 I still got an error when I didn’t have bundler installed. But when I installed bundler the problem went away. I don’t know but when I read the code for the latest release it looked to me like it would fail ugly if bundler wasn’t even installed. But I have not gone back to try again now that I gave my gem library a root canal. I could try if you need me to.
From: Denis Defreyne notifications@github.com @pitosalas Is the issue you’re experiencing #452, rather than this one? — |
Hey,
Having some trouble here with using the
nanoc
executable as installed fresh via RVM. Some system details:I installed nanoc like so:
However, every time I try to run
nanoc
includingnanoc --version
, I get this dreadful error:I have been able to reproduce this even with a clean RVM install (after having nuked RVM with
rvm implode
and then reinstalled stable. Bummer.Let me know what other info I can provide to help move things along.
The text was updated successfully, but these errors were encountered: