You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I'm not sure this is a problem with your rust bindings, but I have not been able to make a similar example work with the libgit2.
It looks like the ssh configuration is not used when accessing remote using ssh.
Then, libgit2 will raise an error when an access to the remote is tried (I have this error in a personal project, but using the ls-remote example yields the same error) :
$ ../testlibgit2/target/debug/testlibgit2 origin
error: failed to resolve address for toto: Name or service not known; class=Net (12)
I suspected an outdated libssh2 on my centos7, so I updated it to 1.8.0 without any difference.
I've also tried using an up-to-date debian sid (that ships with 1.8.0).
Is this a problem of libgit2-rs ? Or should I try to dig in libgit2 ?
The text was updated successfully, but these errors were encountered:
Thanks for the report! Currently libgit2 relies exclusively on libssh2 for ssh support, and libssh2 doesn't read ~/.ssh/config (AFAIK). It'd be great to have support for that though!
Thanks for your reply. After some more search, I've found this: libgit2/libgit2#4338
I guess I can close this issue as it has nothing to do with your bindings.
Hi!
I'm not sure this is a problem with your rust bindings, but I have not been able to make a similar example work with the libgit2.
It looks like the ssh configuration is not used when accessing remote using ssh.
With
.ssh/config
:Then, libgit2 will raise an error when an access to the remote is tried (I have this error in a personal project, but using the ls-remote example yields the same error) :
I suspected an outdated libssh2 on my centos7, so I updated it to 1.8.0 without any difference.
I've also tried using an up-to-date debian sid (that ships with 1.8.0).
Is this a problem of libgit2-rs ? Or should I try to dig in libgit2 ?
The text was updated successfully, but these errors were encountered: