-
Notifications
You must be signed in to change notification settings - Fork 17
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
Unhandled exception on latest Ubuntu 18.04.1 because of upgrade to libcurl4 #13
Comments
AWESOME. Now, these are great bug reports! @ethomson, what's the best way to make LibGitSharp2 workable for me under Ubuntu 18.04.1? It should be pretty popular for our crowd due to WSL support. |
I’m working on reducing the native dependencies that libgit2sharp takes. In the meantime you can try the experimental builds of that (libgit2/libgit2sharp#1618) or continue to require users to install libcurl3. |
@terrajobst If you don't want to wait for the work @ethomson mentioned that will remove the curl and OpenSSL dependencies completely, the latest preview release, 0.26.0-preview-0062, now includes an |
In addition, I've released a prerelease LibGit2Sharp that should help a bit here. I've updated libgit2 to have built-in support for proxies, so we no longer rely upon libcurl. I think this should help the native dependency problems quite a bit. This is available in LibGit2Sharp 0.26.0-preview-0070. |
From ethomson: > I've released a prerelease LibGit2Sharp that should help a bit here. I've > updated libgit2 to have built-in support for proxies, so we no longer rely > upon libcurl. I think this should help the native dependency problems quite > a bit. This should resolve the libcurl4 issue with have on Ubuntu 18.04.1 (#13).
I've pushed an update to nuget.org (git-istage 0.2.61). Will take a few minutes before it's available. To upgrade, run
To install on a fresh box run
|
Running dotnet CLI 2.1.5 on Ubuntu 18.04.1 LTS, git-istage throws this exception:
Turning up LD_DEBUG yields this nugget:
It looks like LibGit2Sharp depends on libcurl3 as referenced in this issue. So this will probably go away when LibGit2Sharp updates their native library.
For completion's sake, my dotnet config:
The text was updated successfully, but these errors were encountered: