Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

what is the expected behavior when the gem was yanked from rubygems? #291

Open
AlexVKO opened this issue Mar 24, 2021 · 0 comments
Open

Comments

@AlexVKO
Copy link

AlexVKO commented Mar 24, 2021

Today the version 0.3.5 of mimemagic was yanked from RubyGems, but the version is cached on our gemstash instance.

I'd expected that it would not break the current fetching, because I can see the gem inside the gemstash directory.

Is that something expected?

Fetching gem metadata from http://172.27.0.1:9292/............
Fetching gem metadata from http://172.27.0.1:9292/.
Resolving dependencies...

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. If you haven't changed sources,
that means the author of mimemagic (0.3.5) has removed it. You'll need to update
your bundle to a version other than mimemagic (0.3.5) that hasn't been removed
in order to install.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant