- Notifications
You must be signed in to change notification settings - Fork 915
Upgrade to libgit2 ff8d635#1049
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
Uh oh!
There was an error while loading. Please reload this page.
Conversation
LibGit2Sharp/packages.config Outdated
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
How did you update this to the 1.0.27 version? Manually? If you do that, then the corresponding targets stuff in the .csproj file doesn't get updated to point to the new package.
To make sure everything gets updated properly, you'll want to update the allowedVersions property first, then run a package update via nuget.
The allowedVersions has to be updated first, otherwise the package update won't be allowed to update to the newer version.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
The allowedVersions has to be updated first, otherwise the package update won't be allowed to update to the newer version.
I've discovered this the hard way 😉 This is part of the things we should document as part of libgit2/libgit2sharp.nativebinaries#2
Thanks a lot for watching my back! 😍
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
FWIW, it took an embarrassingly long time to troubleshoot this. I kept on getting AccessViolationException on tests involving the IndexEntry. The native changes were quite straightforward. I investigated the memory, thinking I was getting padding issues. Which wasn't making any sense as everything was correctly aligned.
...Until I took a look at the libgit2 version being loaded...
And everything unfolded to me being an idiot 😜
Therzok commented May 15, 2015
nulltoken commented May 15, 2015
Current status: |
nulltoken commented May 15, 2015
🎉 All the remaining failing tests are because of the thrown I'm done for today with this. I'll work on tackling the remaining issues tomorrow. |
nulltoken commented May 16, 2015
The only remaining failing tests require a change to libgit2 so that @carlosmn nicely agreed to make those changes. Stay tuned! |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Do we need this?
nulltoken commented May 17, 2015
Depends on libgit2/libgit2#3127 and libgit2/libgit2#3134 |
nulltoken commented May 22, 2015
Current status: The failing test is related to opportunistic updates. The remotetips handler is called twice
@carlosmn Do we actually need the second call? |
carlosmn commented May 22, 2015
The second call is unnecessary, I've updated the branch to skip it. |
nulltoken commented May 22, 2015
|
eff9aa4 to 86e8ac3Comparenulltoken commented May 28, 2015
And the build is passing passing!!!!! |
LibGit2Sharp/Core/GitFetchOptions.cs Outdated
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Is there a reason to do this in the constructor, vs as a field initializer?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Should this be TagFetchMode.Fallback?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I'm not sure. Without it, the tests pass, but something seems weird to me (although I cannot identify what bugs me right now). Dropped it
jamill commented May 28, 2015
👍 awesome! |
nulltoken commented May 28, 2015
@jamill Thanks for the review! Could you please double check the fixup proposal and see if that looks better? |
jamill commented May 29, 2015
@nulltoken looks good, thanks! |
nulltoken commented May 29, 2015
That was a little of a bumpy road, but 🎉 |
whoisj commented May 29, 2015
and I'm already making use of it! 🎉 🎈 |
nulltoken commented Jun 6, 2015
Published as NuGet pre-release package |
coveralls commented Jan 23, 2017
Changes Unknown when pulling 6c12de4 on ntk/upgrade_nuget into ** on vNext**. |

This is an attempt to update to the latest libgit2 while dogfooding the new libgit2 binaries NuGet package.
I've downloaded the Appveyor artifact from libgit2/libgit2sharp.nativebinaries#4 in a local folder. I then reconfigured VS to use this folder as a local NuGet package source.
While going through this process I'm taking notes in order to further update libgit2/libgit2sharp.nativebinaries#5 and fixlibgit2/libgit2sharp.nativebinaries#2.
/cc @bording@jamill