Skip to content
This repository has been archived by the owner on Nov 23, 2020. It is now read-only.

Problem with Gemfile.lock, zeitwerk (2.4.0), and Ruby 2.4.2 #157

Open
jhsu802701 opened this issue Sep 27, 2020 · 2 comments
Open

Problem with Gemfile.lock, zeitwerk (2.4.0), and Ruby 2.4.2 #157

jhsu802701 opened this issue Sep 27, 2020 · 2 comments

Comments

@jhsu802701
Copy link

Is there any good reason that the Gemfile.lock file is listed in .gitignore and thus not saved in this repository? This is causing a problem.

Here's an example of the "but it works on my machine" problem. If you set up this app on a particular machine some time ago, it still works. But if you try to start a new setup right now, you get an error message during "bundle install" stating that zeitwork 2.4.0 requires at least Ruby version 2.4.4. The current Ruby version specified for this app is 2.4.2.

This wouldn't be a problem on an old setup, because its Gemfile.lock file would specify something older than version 2.4.0 of zeitwork, a version that is compatible with Ruby 2.4.2.

@jhsu802701
Copy link
Author

The solution is in Pull Request #159 .

@jhsu802701
Copy link
Author

The solution is in Pull Request #161 .

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

No branches or pull requests

1 participant