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

Update Excon version to use >= 0.46 #449

Closed
wants to merge 1 commit into from

Conversation

yitsushi
Copy link

with older version of Excon, Docker responses with '400 Bad Request'

If you install this gem now, it's not a problem, but if you installed it before Excon=0.46
then docker-api gem installed excon and later updates don't require an update on excon.

Original issue: #381

Related issue: excon/excon#547

because with older version of Excon, Docker responses
  with '400 Bad Request'

Related issue: excon/excon#547
@yitsushi
Copy link
Author

About "All checks have failed":
There were 4 failed job. All of them was "gpgkeys: key xxxx can't be retrieved" and because of this docker install was failed. Where docker install was successful, tests could run without error.

@tlunter tlunter closed this Sep 26, 2016
@tlunter
Copy link
Contributor

tlunter commented Sep 26, 2016

I won't force people to update excon unless they are hitting this problem. Excon is used by lots of other gems. It's already noted in the README.

@yitsushi
Copy link
Author

yitsushi commented Sep 26, 2016

A question: If anyone uses old version of this gem and want to update it. Is there any way that they don't have to update excon? I mean with new docker and new docker-api gem, I could not find on 7 servers when I don't have to update excon also.

(if they don't want to update, they are not affected with this but they don't get the now gemspec also)

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

Successfully merging this pull request may close these issues.

2 participants