hello who can help me with this gem
Did you solve it?
What command were you trying to execute?
such errors disappear when
bundle update is executed instead of bundle install
If the error is persistent, delete Gemfile.lock, and repeat bundling
Be careful with this.
Maybe it will solve it, maybe not. But definitely the Gemfile.lock has a reason to be in the current state and you should not modify it manually (like deleting it), unless you are conscious of the consequences.
That file is meant to be managed by bundler itself, and when you delete it, is like doing a big restart of the project, which is ok untill the project is developed by more than one developer, or being run in more than one machine.
So context is important here. Provide more of it and we can assist better. Maybe in your case it is as easy as the previous message suggest. But maybe not.
If a project is properly setup, there is no harm deleting Gemfile.lock
You can always restore it from the git-history.
Usually,
bundle updatedoes the job.
If a gem does not integrate easily in the context, its best not to use it altogether.