Closed muratseyhan closed 8 years ago
Thanks for the report. We're you able to capture the rubygems version that raised the error?
It seems like this is probably something in the gemspec that depends on a recent version. Depending on how far back we need to support, I'm happy to sort out compatibility.
Okay, so answering issues from a phone means you'll miss relevant details. I'll see if I can repeat with 2.5.1.
This looks to be related to https://github.com/rubygems/rubygems/issues/1420.
Since this is treated as a bug upstream, I'm going to close it and defer to their solutions.
Using RubyGems 2.5.1, I tried the following instructions from
README.md
.I received the following error.
Updating RubyGems seems to solve the problem.