-
Notifications
You must be signed in to change notification settings - Fork 29
Provision fails with errors #98
Comments
To add: I've already run |
Further developments: It looks like commands in |
Further developments: The only way to run One other side-drawback is for people like me, that have passphrases on keys used with github, is that I have to type it in for each single package cloned or at least this is what it prompts me to do. |
I agree that the shell script to close those repositories should be changed to use HTTPS over the git:// protocol. This removes the need of having SSH keys on the server and on GitHub. Fortunately, it is fairly easy to switch this with a couple of commands in vim: :%s/git@/https:///g This should be the default behaviour ,though, in my opinion. |
Yes sounds good. Could either of you do a Pull Request, please? |
I have submitted pull request #105 to make these changes. All git clone commands reference HTTPS URLs now, including the two in the README.md file. :) |
Host is 64 bit linux.
First error looks like to be:
The entire output is:
The text was updated successfully, but these errors were encountered: