Skip to content
This repository has been archived by the owner on Apr 14, 2021. It is now read-only.

Bundler reports issues in Gemfile.lock regardless of the file being used as gemfile #3672

Closed
AgentAntelope opened this issue May 22, 2015 · 3 comments · Fixed by #3677
Closed

Comments

@AgentAntelope
Copy link

For example, in the event of a merge conflict in the file GemfileFast, bundler provides the following error:

screen shot 2015-05-22 at 10 58 58

@richbowen
Copy link

Can you provide more information following the guidelines in ISSUE.

@segiddins
Copy link
Member

@rgb-one no additional info needed.

Yes, there are places where we hardcode Gemfile.lock where we shouldn't.

@AgentAntelope
Copy link
Author

Thanks, @segiddins.

I've had a bit of a look at this in an attempt to fix it. It seems that the LockfileParser, which generates this error, has no knowledge of the filename of the file it's trying to parse. I attempted to give it that information, but the assumptions seems to be baked in in quite a few places; Not just the lockfile parser, but the lockfile helper method, and other places too.

Sadly I think this is too large a piece of work for me without knowing more about the direction the code is headed in.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants