-
Notifications
You must be signed in to change notification settings - Fork 2.6k
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
ASIHTTPRequest (1.8.1) Problem #195
Labels
t2:defect
These are known bugs. The issue should also contain steps to reproduce. PRs welcome!
Milestone
Comments
Hmm, I thought I had double-checked the versions of rake that ship with the stdlib in various Ruby versions. Please install the ‘rake’ gem, that should fix this. I’ll leave the ticket open so that we know to add the correct rake version to the gem spec for the next release. |
Did so and indeed: fixed ! Thank you and greetings from Berlin |
Thanks for verifying! Greetings from Amsterdam :) |
goonzoid
pushed a commit
to goonzoid/CocoaPods
that referenced
this issue
May 25, 2012
* master: Minor copy change A few small fixes related to integrating multiple targets/projects. Add rake ~> 0.9.0 (for rake/file_list.rb file) to gemspec. Closes CocoaPods#195. Fix for CocoaPods#141 [Push] Bypass pre-commit hook. [Fix] GitHub downloader was downloading the repos twice. Conflicts: spec/unit/resolver_spec.rb
jzapater
pushed a commit
to jzapater/CocoaPods
that referenced
this issue
Sep 17, 2013
dd back commit hash for vfrReader
alloy
added a commit
that referenced
this issue
Oct 25, 2014
fabiopelosin
added a commit
that referenced
this issue
Oct 25, 2014
* master: Minor copy change A few small fixes related to integrating multiple targets/projects. Add rake ~> 0.9.0 (for rake/file_list.rb file) to gemspec. Closes #195. Fix for #141 [Push] Bypass pre-commit hook. [Fix] GitHub downloader was downloading the repos twice. Conflicts: spec/unit/resolver_spec.rb
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
t2:defect
These are known bugs. The issue should also contain steps to reproduce. PRs welcome!
first run leads to the following:
The text was updated successfully, but these errors were encountered: