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

Switch to Github API v3. (v2 was turned off on 6/1/2012.) #19

wants to merge 1 commit into
base: master


None yet
5 participants
Copy link

yipdw commented Jun 14, 2012

This is a quick "works for me" hack. Let me know if there's stylistic guidelines, tests, etc. that you'd like to see.


This comment has been minimized.

Copy link

tolland commented Jun 15, 2012

works for me. cheers.
chef (0.10.10)
$ ruby -v
ruby 1.9.2p320 (2012-04-20 revision 35421) [x86_64-linux]


This comment has been minimized.

Copy link

geewiz commented Jun 30, 2012

Fixed the problem here, too. Chef 10.12.0, ruby 1.9.2p290 (2011-07-09 revision 32553) [x86_64-darwin11.3.0]


This comment has been minimized.

Copy link

nphase commented Jul 2, 2012

Fixed the problem here too, same specs as geewiz. +1


This comment has been minimized.

Copy link

dfuentes77 commented Jul 14, 2012

Manually patching didn't work for me as to this problem. I'm trying to install this cookbook and I keep getting the following error:

$ knife cookbook github install fnichol/chef-rvm/v0.9.0
Installing rvm from git:// to /Users//chef/.chef/../cookbooks
Checking out the master branch.
Pristine copy branch (chef-vendor-rvm) exists, switching to it.
Removing pre-existing version.
ERROR: The object you are looking for could not be found

$ gem list chef
chef (0.10.10)
$ knife -v
Chef: 0.10.10
$ ruby -v
ruby 1.9.2p290 (2011-07-09 revision 32553) [x86_64-darwin11.4.2]

@tjdett tjdett referenced this pull request Aug 6, 2012


Updating to Github API v3 #21


This comment has been minimized.

Copy link

nphase commented Aug 8, 2012

I've merged pull request #21 (contains this one) into my master ( which is what is pointing to as of today. update/cleanup your gem and things should be good to go.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment