-
Notifications
You must be signed in to change notification settings - Fork 33
Deleted Git related projects from solution. #28
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
Conversation
on my machine (mint 20 = ubuntu 20.04), git-related projects compile without problems (https://github.com/dotdevelop/dotdevelop/tree/dotdevelop_oe_8.2.6). what errors you get? |
& dotnet-sdk-5.0 : i've dotnet-sdk-3.1, working too. |
LibGit2Sharp failed to compile with a famous error of its own. I will try to use a Travis CI clean VM then since your machine works. |
Have you managed to track down the LibGit2Sharp error yet? I still get this on clean VMs (both ubuntu and Arch) and can't seem to get to the bottom of it. Any help would be appreciated. |
what error you get exactly? |
I tried several VMs, and always got
|
i'm just trying on a plain ubuntu 20.04, same error as you. |
Yes, that's exactly what I'm getting - and it's the same on a plain fedora VM as well. However, like you, on my main (Arch) PC, it compiles with no errors! I've tried building LibGit2Sharp with msbuild -v:d LibGit2Sharp.csproj but I'm no nearer finding the difference. The file that can't be found (lib/linux-x64/libgit2-106a5f2.so) is correct in the libgit2sharp.dll.config file, and is in the right place, so I don't understand why it can't be found. |
On dotdevelop-8.2.6 I get just the 1 error (the Nerdbank.GitVersioning one listed for 8.4.3), but not the other one. I wonder what @lextm meant by "a famous error of its own"? |
Hey guys, keep up the good work! But if you want more clarity on what can still build or not, maybe we have to setup a quick GithubCI lane? I did one recently for macOS (check this: mono#9174 ) and shouldn't be hard to make it run on Ubuntu 20.04 LTS. |
@knocte Yeah, setting up a CI pipeline should be a good way to guarantee that everyone is on the same page (instead of relying too much on individual machines). But the tricky part right now is LibGit2Sharp fails to compile on clean Ubuntu 20.04 machines (I tried 3, and others tried several as well). So I think the core question here is whether to investigate and resolve the LibGit2Sharp compilation issue first. To me, it is more important to have a working CI pipeline with succeeded builds, so I rather remove all Git projects from the solution and have the main code base built and shared among contributors (the goal of this pull request). Users requiring Git can always use another Git client, and contributors can later revisit LibGit2Sharp and see how to resolve it (but it has been a famous issue so I don't expect it is easy to fix). |
Well, it seems that the CI goal wouldn't be possible without this PR anyway, so maybe it should be included in this PR. I mean, to make your point crystal clear you could add the GithubActions CI lane as a first commit in this PR (and as you say, its status would be red, as in failing), and then your second commit would fix it (and it would be marked with a green icon). |
I started an issue about CI: |
I started an issue about MonoDevelop.VersionControl.Git: |
Tested on an Ubuntu 20.04 machine, and the problematic projects must be removed from the solution for the code base to compile without errors.
The following packages are required, but not documented in README-oe-modifications.txt,