Skip to content
This repository has been archived by the owner on Aug 19, 2023. It is now read-only.

Bundle is locked to logger (1.2.8) which has been yanked #459

Open
BenKettlewell opened this issue Dec 18, 2018 · 2 comments
Open

Bundle is locked to logger (1.2.8) which has been yanked #459

BenKettlewell opened this issue Dec 18, 2018 · 2 comments
Labels
Milestone

Comments

@BenKettlewell
Copy link

$bundle install
Fetching gem metadata from https://rubygems.org/.......
Your bundle is locked to logger (1.2.8), 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 logger (1.2.8) has removed it. You'll need to update your bundle to a version other than logger (1.2.8) that hasn't
been removed in order to install.

Logger v1.2.8 was yanked and bundle install won't build.

Logger Issue

@BenKettlewell
Copy link
Author

Modified Gemfile.lock logger version to 1.3.0 and I was able to successfully get everything up and running.

@i128 i128 added the bug label Jan 6, 2019
@i128 i128 added this to the v0.7.5 milestone Jan 6, 2019
@felixhertrampf
Copy link

You can script the change to 1.3.0 with:

sed -i "/logger/s/$/, '~> 1.3', '>=1.3.0'/" Gemfile

You have to be in the hashview dir oc.

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

No branches or pull requests

3 participants