-
Notifications
You must be signed in to change notification settings - Fork 357
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
Checksum validation fails for faraday_middleware-0.11.0.gem #787
Comments
We have created an issue in Pivotal Tracker to manage this: https://www.pivotaltracker.com/story/show/141183785 The labels on this github issue will be updated when the story is started. |
Hey @kdykeman , Thanks for submitting this issue. It does look like this is a known faraday_middleware / rubygems issue. However, we are only pulling in this gem because of Thanks, |
A link for more information: rubygems/bundler#5332 |
The linked issues seem to indicate that azure gem has been updated and we can bump it to get the updated version of faraday_middleware. Reopening until we rule out bumping the dependency. |
Thanks @zrob, I spotted that today as well when looking upstream. |
The chain is: |
- Checksums were wrong on rubygems which angered new version of bundler [#141183785][#787] Signed-off-by: Jonathan Berkhahn <jaberkha@us.ibm.com>
@kdykeman a fix should be available on master now. Would mind verifying that you are able to bundle? thanks! |
@zrob Thanks! I am now able to bundle. |
Issue
When running
bundle install
the following disconcerting message comes up:Context
See rubygems/bundler#5332
Steps to Reproduce
Run
bundle install
Expected result
Bundler doesn't complain about the checksums not matching.
Current result
Bundler complains about the checksums not matching (see screenshot)
Possible Fix
Update to a newer version of faraday_middleware where the community asserts the checksums match.
name of issue
screenshotThe text was updated successfully, but these errors were encountered: