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

Error when installing new repo #8

Open
patcon opened this issue Jun 24, 2011 · 3 comments
Open

Error when installing new repo #8

patcon opened this issue Jun 24, 2011 · 3 comments

Comments

@patcon
Copy link

patcon commented Jun 24, 2011

Hey Jesse,

Any idea what might be causing this? I'm trying to install a new repo, and it seems like it's expecting the dir to be there already... I've tried both fresh (without a chef-vendor-drush branch being present, and with it).

Thoughts?

{code}
$ knife cookbook github install msonnabaum/chef-drush
zsh: correct 'cookbook' to 'cookbooks' [nyae]? n
Installing drush from git://github.com/msonnabaum/chef-drush.git to site-cookbooks
Checking out the master branch.
Pristine copy branch (chef-vendor-drush) exists, switching to it.
Removing pre-existing version.
ERROR: Chef::Exceptions::ShellCommandFailed: Expected process to exit 0, but it exited with 1
---- Begin output of mv _tmp_chef_drush site-cookbooks/drush ----
STDOUT:
STDERR: mv: rename _tmp_chef_drush to site-cookbooks/drush: No such file or directory
---- End output of mv _tmp_chef_drush site-cookbooks/drush ----
Ran mv _tmp_chef_drush site-cookbooks/drush returned 1
{code}

@patcon
Copy link
Author

patcon commented Jun 24, 2011

Ahh... figured it out. knife.rb allows for you to just put in cookbooks like "site-cookbooks", and it takes this as root of the chef-repo, but it seems knife-github-cookbooks is expecting an absolute path

@patcon
Copy link
Author

patcon commented Jun 24, 2011

Goes without saying, but for those who commit their .chef folder as well, it makes it tough. I'll see if I can dig in later and figure it out :)

@sumbach
Copy link

sumbach commented Oct 30, 2011

Submitted a pull request with a proposed fix. See #14 for details.

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

No branches or pull requests

2 participants