-
Notifications
You must be signed in to change notification settings - Fork 282
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
Rugged::Repository.clone_at over ssh fails #366
Comments
What's your version of libssh2? Do you have it in your load path? What does |
libssh2 version 1.4.3
|
Your library isn't linked to libssh2 (or openssl which is also weird). It shouldn't even have linked successfully. It's very odd. Does this only happen when you try to clone over ssh? Do other operations work? |
Yep. Tried reading/writing a local repo and that works. Cloning a remote repo over https works too. |
One note is that libssh2 is installed from source and the files are in The server is a Ubuntu 12.04 instance running on AWS. |
What are the contents of libgit2's pc file? It should be at |
Actually, since rugged builds its own copy, it would be under wherever you build the gem, and then under |
|
I can't reproduce this on my ubuntu VM. It is a 14.04, I'll see about grabbing a 12.04 version. The file looks correct. What does |
That produces this:
Thanks for helping me debug. I'm pretty unfamiliar with this level of the stack. |
Is there a way to more explicitly specify the path to libssh2 in the build process? |
You can export that line from pkg-config as |
So it turns out that chef was putting it's version of pkg-config at Sorry for the bother. |
Hello. I installed the plugin on redmine "redmine_git_hosting". An error when I change the settings. |
With the latest update of rugged, I'm now getting the above error from clone_at when using ssh credentials.
The text was updated successfully, but these errors were encountered: