Bundle update in 1.7.0 ignores gem list

[aselder]

I have a decent size project, and ran bundle update tzinfo. Imagine my surprise when ~30 odd gems got updated, most that are not related to tzinfo. I reverted and compared the output to a raw bundle update and got an exact match.

I reverted back to bundler 1.6.5 and ran bundle update tzinfo, and got the expected result, only the tzinfo gem was bumped.

[aselder]

FWIW, this was under Jruby 1.7.13

[TimMoore]

@aselder could you please try the prerelease version of Bundler 1.7.1 and let us know if that solves your problem?

Install with gem install --pre bundler.

[jimeh]

I ran into the same issue with 1.7.0, but when running bundle install during which nothing should be updated. Here's a sample of it's output:

Using listen 1.2.2 (was 0.7.3)
Using lumberjack 1.0.4 (was 1.0.3)
Using method_source 0.8.2 (was 0.8.1)
Using slop 3.5.0 (was 3.4.4)
Using pry 0.9.12.2 (was 0.9.12)
Using guard 1.8.1 (was 1.6.2)
Using guard-jasmine 1.10.1
Using guard-rspec 3.0.2 (was 1.2.1)

Tried with 1.7.1.pre.3 and it behaves like normal again.

[cimm]

Seems this is related to #3136 and should be fixed in Bundler 1.7.1 when it's released.

[Tonkpils]

Not sure if this is tied with #3150 and according to this comment #3136 (comment) , when I ran bundle install with bundler 1.7.1.pre.3 the auth info is back on the Gemfile.lock

[indirect]

Bundler 1.7.1 (final) is released, and has fixes for the updating issues. It also restores byte-wise compatibility with Bundler 1.6.x and Gemfiles containing credentials.

On Fri, Aug 22, 2014 at 12:26 PM, Leo Correa notifications@github.com
wrote:

Not sure if this is tied with #3150 and according to this comment #3136 (comment) , when I ran bundle install with bundler 1.7.1.pre.3 the auth info is back on the Gemfile.lock

Reply to this email directly or view it on GitHub:
#3149 (comment)

[hone]

@indirect I think we still need to release 1.7.1.

[TimMoore]

Fixed in 1.7.1.