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

getting started guide on gembundler.com seems wrong #749

Closed
johnl opened this Issue Oct 7, 2010 · 3 comments

Comments

Projects
None yet
2 participants
@johnl

johnl commented Oct 7, 2010

follwoing the getting started guide on gembundler.com, it says to install bundler, ensure you're on ruby 1.3.6 or above, specify your gems in a Gemfile (which I've done). Then it says to run "bundle install" but when I do this I get this error message:

You have modified your Gemfile in development but did not check
the resulting snapshot (Gemfile.lock) into version control

You have added to the Gemfile:

I don't have a Gemfile.lock, and the guide doesn't mention how to create one :/

@indirect

This comment has been minimized.

Show comment
Hide comment
@indirect

indirect Oct 12, 2010

Member

Sorry for the delay getting back to you -- I didn't understand your explanation the first time I read it, for some reason.

You found a bug! You must have run bundle install --deployment before running bundle install. Please run rm -rf .bundle && bundle install to solve your problem. I'll work on fixing the bug you found and report here when it's done.

Member

indirect commented Oct 12, 2010

Sorry for the delay getting back to you -- I didn't understand your explanation the first time I read it, for some reason.

You found a bug! You must have run bundle install --deployment before running bundle install. Please run rm -rf .bundle && bundle install to solve your problem. I'll work on fixing the bug you found and report here when it's done.

@indirect

This comment has been minimized.

Show comment
Hide comment
@indirect

indirect Oct 12, 2010

Member

Allow installing after --deployment fails due to missing lock

Breaking things after there was an error really, really sucks. Closed by 5df892e.

Member

indirect commented Oct 12, 2010

Allow installing after --deployment fails due to missing lock

Breaking things after there was an error really, really sucks. Closed by 5df892e.

@johnl

This comment has been minimized.

Show comment
Hide comment
@johnl

johnl Oct 12, 2010

Yes, I discovered that rm -rf .bundle and bundle install fixed it. Thanks!

Sorry that I didn't come back to update, the high number of bug reports that appeared to have had no activity made me think this bug tracker was dormant! (sorry!)

johnl commented Oct 12, 2010

Yes, I discovered that rm -rf .bundle and bundle install fixed it. Thanks!

Sorry that I didn't come back to update, the high number of bug reports that appeared to have had no activity made me think this bug tracker was dormant! (sorry!)

joevandyk pushed a commit to joevandyk/bundler that referenced this issue May 16, 2011

Allow installing after --deployment fails due to missing lock
Breaking things after there was an error really, really sucks. Fixes bundler#749.

This issue was closed.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment