-
-
Notifications
You must be signed in to change notification settings - Fork 2k
Bundle install --deployment fails with Gemfile.lock is corrupt #5044
Comments
@segiddins my best theory at the moment is that this is a result of the development dependencies change you made to |
Thanks, all -- let me know if I can be of any further assistance debugging etc. I'm more than happy to help if I can. |
Confirmed, thanks for the repro case! |
So my one question is, how did you get this lockfile? Since if I |
@segiddins based on comments from an earlier ticket, I believe this lockfile was generated by Bundler 1.11 |
Then it would appear that we fixed a bug in the meantime -- the error is correct, that lockfile is wrong |
I'm still seeing the issue, here's a demo:
|
@segiddins even if we fixed a bug, we need to ensure that actually working lockfiles continue to actually work 👍 |
@trevorturk you need to install with the fixed version of bundler @indirect the point of that check is that those lock files always were broken |
Can you have a closer look at that demo I posted in the comments here? I believe I am installing with the version of bundler you want:
|
but it's not changing the version in the lockfile, which has me suspicious. When I |
Okay... this is super weird. @trevorturk, this is working for me too.
|
hoooo boy. okay, this is pretty fucking weird. @segiddins, this only reproduces with both
|
Lockfiles that raise exceptions only when |
@segiddins note further that this happens even after using Bundler 1.13.2 to generate a completely new lock from scratch:
|
Hmm, I don't know what could be different about my setup. Here's my env:
The repo I linked to has the lock file set to 1.13.2 so I wouldn't expect it to change the version in the lock file. |
@trevorturk thanks for bearing with us while we figured out exactly how to reproduce it. |
Possibly-related discovery by @segiddins: according to rubygems.org, the sinatra-sequel gem somehow depends on bacon as both a runtime and development dependency, separately. https://rubygems.org/gems/sinatra-sequel/versions/0.9.0 |
Hmm... I'm not sure what else to try w/r/t identifying what's different about my env. I tested updating my rubygems and I can still reproduce:
I'm using rbenv, in case that might be a difference with my setup:
If you have any other ideas, I'm happy to test. I mentioned this before, but I'm also happy to screen share etc if that might help. Thanks again for continuing this hunt. I sure hope I'm not doing something stupid and sending us on a wild goose chase! 😅 |
reminder to < |
This is a followup re: #4467, #5006, and #5008 with steps to reproduce the issue I'm seeing that I don't believe has been fixed by version 1.13.2:
https://github.com/trevorturk/bundler-test-5006
The issue can be worked around by replacing
sinatra-sequel
with my forked gem rtomayko/sinatra-sequel@master...trevorturk:no-bacon that removes anadd_development_dependency
line which seems to be causing the error. The change to the Gemfile would be:gem 'sinatra-sequel', github: 'trevorturk/sinatra-sequel', branch: 'no-bacon'
The text was updated successfully, but these errors were encountered: