You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
"bundle install" fails with: Your bundle is locked to mimemagic (0.3.5), but that version could not be found in any of the sources listed in your Gemfile.
#27
Open
Benmuiruri opened this issue
Dec 14, 2022
· 1 comment
When I clone the repo and try bundle install the operation fails with
Your bundle is locked to mimemagic (0.3.3), but that version could not be found
in any of the sources listed in your Gemfile. If you haven't changed sources,
that means the author of mimemagic (0.3.3) has removed it. You'll need to update
your bundle to a version other than mimemagic (0.3.3) that hasn't been removed
in order to install.
Some suggestions on StackOverflow suggest running bundle update --conservative mimemagic , which works, and the gems are installed.
The other option that also works is deleting the Gemfile.lock file and then running bundle install.
However, when I start the development server and then visit localhost:3000 the server shuts down and I get a very long cryptic error as shown in the two screenshots.
The text was updated successfully, but these errors were encountered:
I was able to solve the issue 😄 From the error I saw that its the pg gem that was causing the error.
After applying my technical sophistication on Google it turns out the host value should be blank. So instead of this ..
Hello team.
When I clone the repo and try
bundle install
the operation fails withSome suggestions on StackOverflow suggest running
bundle update --conservative mimemagic
, which works, and the gems are installed.The other option that also works is deleting the
Gemfile.lock
file and then runningbundle install
.However, when I start the development server and then visit
localhost:3000
the server shuts down and I get a very long cryptic error as shown in the two screenshots.The text was updated successfully, but these errors were encountered: