-
Notifications
You must be signed in to change notification settings - Fork 5.5k
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
gitfs: Fix use of deprecated pygit2 function #51304
Conversation
abbaa72
to
3eb5e74
Compare
0.27.4 (released 5 days ago) removed pygit2.Reference.get_object()
3eb5e74
to
c02757d
Compare
@terminalmage what is the best way to backport this to Fedora since this is now broken there? |
@toanju What Fedora are you using where 0.27.4 is available in the repositories? I think only F30 is affected but it's still in beta. In the meantime, you'd have to either install pygit2 version 0.27.3 or apply the patch from this pull request. If you decide to do the latter, you can get the patch by adding |
@terminalmage F29 got this as well https://apps.fedoraproject.org/packages/python-pygit2 In any case what is the best workflow to bring this upstream? A new issue here or in the Bugzilla of Red Hat or directly a PR to src.fedoraproject.org? Thanks for the feedback :) |
The RedHat Bugzilla is probably a good place to start. Just mention that the fix is https://github.com/saltstack/salt/pull/51304.patch. |
+1 (need to use pip on EL7 when using your py3 packages or you should provide the package python3.6-pygit2) |
For some reason, this pull request has been merged into saltstack:2018.3, but I use a 2019.2.0 install on archlinux and the commit is not applied. Is it normal ? |
This bugfix was merged after the 2019.2 release branch was frozen for the 2019.2.0 release. The fix will be part of the 2019.2.1 release. |
Thanks for the information. I manually applied the patch until 2019.2.1 comes out. |
If this Bugfix was merged into 2018.3 why do I encounter this bug in 2018.3.4 with pygit2: 0.28.2 @terminalmage ?
|
Because they'd already branched 2018.3.4 from the 2018.3 release branch in preparation for the 2018.3.4 release, is my guess. |
Ok, I understand that. But which is the combination of software and libraries I have to use to get gitfs back to work? #54165 |
Pygit2 0.27.3 and any libgit2 0.27.x release should work. The OP at the top of this pull request states that this PR is in reaction to a change that was made in Pygit2 0.27.4, so I'm not sure why this seems strange to you. You can:
|
Thank you very much for your patience!
|
0.27.4 (released 5 days ago) removed
pygit2.Reference.get_object()
. This fixes it so that older pygit2 still works, while using.peel()
where applicable.Resolves #51270.