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

Can't get make run to compile Vico with permission-related git-submodule messages. #43

Closed
godDLL opened this issue May 13, 2013 · 5 comments

Comments

@godDLL
Copy link

godDLL commented May 13, 2013

@Shadowfiend the cryptic submodule-related message is still there.

$ make run
…
Submodule 'plblockimp' (https://github.com/landonf/plblockimp.git) registered for path 'plblockimp'
Submodule 'sparkle' (https://github.com/andymatuschak/Sparkle.git) registered for path 'sparkle'
Cloning into 'Bundles/vicoapp-ack.vico-bundle'...
Permission denied (publickey).
fatal: The remote end hung up unexpectedly
Clone of 'git@github.com:vicoapp/ack.vico-bundle.git' into submodule path 'Bundles/vicoapp-ack.vico-bundle' failed
make: *** [/Users/yuli/Downloads/vico/build/DEBUG/gitmodules.stamp] Error 1
#12:53:33!2 vico:merged$ 
@Shadowfiend
Copy link
Member

Got it. Okay, so Github URLs don't work quite the way I thought. git@github.com:vicoapp/ack.vico-bundle.git would work for you even if you're not a contributor, but would give you a read-only repository (i.e., push wouldn't work). However! It tries to clone via SSH.

Do you currently have a public key configured in Github?

@godDLL
Copy link
Author

godDLL commented May 13, 2013

I installed GitHub for Mac at some point, so yes. How do I get around that issue?
If I remove the key I get this:

fatal: Needed a single revision
Unable to find current revision in submodule path 'Bundles/vicoapp-ack.vico-bundle'
make: *** [/Users/yuli/Downloads/vico/build/DEBUG/gitmodules.stamp] Error 1

EDIT: which is normal because the build target dir is unclean.

@godDLL
Copy link
Author

godDLL commented May 13, 2013

Deleting and re-adding the GitHub key, followed by a make clean and rm -Rf Bundles/* build/* solved it. I've literally been stuck in this situation for months. Thanks @Shadowfiend !

@godDLL godDLL closed this as completed May 13, 2013
@Shadowfiend
Copy link
Member

Still an odd one. We could switch the submodule references to use non-SSH paths, but that would make it more difficult to work on the bundles (you'd have to clone them separately). A nightly is probably a better solution.

@godDLL
Copy link
Author

godDLL commented May 13, 2013

I'd like to stress that just deleting the faulty 'older' (the same as now, btw) SSH key did not fix it. I had to add it anew, so yes. Nightly is the way. :D

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