-
-
Notifications
You must be signed in to change notification settings - Fork 2k
Gemfile.lock Changes Randomly #1081
Comments
It's not random, it's rails 1.5 - 1.6 ordering differences, I have an unfortunately non-working patch for the issue. |
@raggi Please explain. I'm uncertain what you're referring to by 1.5 - 1.6 since there was never a version of Rails with those numbers and the reporter says he sees it with Rails 3 and outside Rails projects. |
Do you mean Rubygems 1.5 - 1.6? I am seeing the Gemfile.lock flip back and forth in order while using Rubygems 1.3.7 exclusively. |
To modify the file all I need to do is run: bundle check -I reset the file using git checkout Because this is happening on one machine, I don't think this can be the result of differing versions of rubygems. I'm running rubygems 1.6.2 and REE 1.8.7 under RVM. Thanks for all the great work on bundler. I'm sure we'll get this sorted out soon! |
This is fixed here: |
@raggi Your patch fixes a different issue from the issue reported here. From what I can tell, your patch only affects the ordering of the lock file between parenthesis. The issue reported here is about the order of the lines within the lock file as illustrated by the gist from the opening post. I just don't want this issue to be prematurely closed by a different issue being fixed. |
I'm also seeing this issue with RubyGems 1.6.2 / bundler 1.0.10 / REE 1.8.7 (2011.03). Running |
Running the same stack as h3h, i have to run |
I'm seeing this every day too. I assume @raggi's pull req would fix the issue.
Bundler 1.0.10, rubygems 1.6.2, rails 3.0.5, ruby 1.9.2 |
If it's helpful. |
My patch fixes mperhams case. It does not fix the net-scp case. I believe @indirect already fixed the net-scp case. If both fixes were rolled into a release, that would be great. |
I'm still seeing the net-scp version of this issue on bundler 1.0.11, FWIW. |
Same here. |
I've been seeing this with |
That's correct, the issue with |
Upgraded to bundler 1.0.12 and the issue persists:
The changes in Gemfile.lock do not go away after running |
...how is that a change? the lines are in the same order. |
Sorry about that, left out lines (updated previous comment) screenshot: http://yfrog.com/h3vm0cj |
Yes, that is the correct sorting. Check that in, and running |
thanks, worked like a charm! |
I'm still seeing this issue on Bundler 1.0.13. Each time I open a Rails console or run a Rake task, I get a change in Gemfile.lock where net-scp has jumped a line down. It basically looks like this:
The changes in Gemfile.lock:
This occurs for me with Ruby Enterprise Edition 1.8.7 (2011.03) and Bundler 1.0.13. Does anybody else see this behavior? What can I do to fix it? |
If you leave it in the order with the version number lower, it should stay in that location, I think. indirect indicates that this is the correct order and that it is not consistent. |
Hm, I've now committed the Gemfile.lock with changed ordering. Will see if it stays unchanged now. Thanks!
|
Had issues similar to: - rubygems/bundler#1375 - rubygems/bundler#1081 Was a problem with the Ubuntu packaged version of bundler. Seems to be resolved in later versions of bundler.
I've started seeing the same issue a couple of weeks ago. The gems installed from github reshuffle randomly from time to time. |
Please upgrade to Bundler 1.7.2 and report back if the problem still exists. On Fri, Sep 5, 2014 at 7:06 AM, Ellin Tolstov [email protected]
|
I'm using |
@fenelon please open a new issue and include the output from |
tl;dr: When loading the project environment (Bundler.setup?) one line in the Gemfile.lock switches places with the line below it.
https://gist.github.com/876573
The above is from a Rails 3 project using bundler 1.0.10 on an Ubuntu 10.10, but I'm seeing similar behavior (a different line in the Gemfile.lock) in other, non-Rails projects that use bundler and on other machines (OS X). I'll continue to play with this an add details as I track it down.
The text was updated successfully, but these errors were encountered: