Bundler deployments with capistrano, now complaining about Gemfile.lock

[Brian Cardarella]

I've been using Bundler and Capistrano in deployment for quite a while
with no issues. Recently I started getting this message:

* executing "bundle install --gemfile /home/deploy/tapology/releases/
20101122042606/Gemfile --path /home/deploy/tapology/shared/bundle --
deployment --quiet --without development test"
servers: ["staging.tapology.com"]
[staging.tapology.com] executing command
** [out :: staging.tapology.com] You have modified your Gemfile in
development but did not check
** [out :: staging.tapology.com] the resulting snapshot
(Gemfile.lock) into version control
** [out :: staging.tapology.com]
** [out :: staging.tapology.com] You have added to the Gemfile:
** [out :: staging.tapology.com] * source: source at /home/deploy/
tapology/releases/20101122042606
** [out :: staging.tapology.com]
** [out :: staging.tapology.com] You have deleted from the Gemfile:
** [out :: staging.tapology.com] * source: source at .

I've downgraded to previous versions of Bundler on both local and on
the server, I've deleted the .bundle directory, I've blown away the
cached-copy directory and of course I've regenerated Gemfile.lock
multiple times. Any thoughts?

[Brian Cardarella]

This is with Bundler 1.0.7

- Brian

[Blake Miller]

Installing bundler 1.0.6 fixed this issue for us

Sent from my iPhone

> --
> You received this message because you are subscribed to the Google Groups "ruby-bundler" group.
> To post to this group, send email to ruby-b...@googlegroups.com.
> To unsubscribe from this group, send email to ruby-bundler...@googlegroups.com.
> For more options, visit this group at http://groups.google.com/group/ruby-bundler?hl=en.
>

[Blake Miller]

Is the source directory indicated correct? This was the prob we ran into where bundler wasn't resolving the path to an engine correctly(relative path to vendor/bundle).

Sent from my iPhone

[Brian Cardarella]

1.0.6 was yanked.

[Brian Cardarella]

Oh yeah, no deal on the path issue either.

I ran the same command on my local machine but set the paths to the
proper ones. Now I'm getting the message there too.

- Brian

[Brian Cardarella]

So I'm debugging 'bundle install' and in the
'ensure_equivalent_gemfile_and_lockfile' method I'm getting this for
the difference between the @sources and @locked_sources:

[#<Bundler::Source::Path:0x1024be7d8 @path=#<Pathname:/Users/
bcardarella/work/tapology>, @version=nil, @name=nil,
@allow_remote=false, @options={"path"=>#<Pathname:/Users/bcardarella/
work/tapology>}, @allow_cached=false, @glob="{,*/}*.gemspec">]

Any clues?

- Brian

[Blake Miller]

Can u post your gemfile?

Sent from my iPhone

[Brian Cardarella]

http://pastie.org/1320072

Thanks for taking a look.

- Brian

[Brian Cardarella]

I found the answer.

path was being defined at the top of the Gemfile. This caused the
issues. I removed it and everything works fine.

- Brian