Closed x70b1 closed 4 years ago
@x70b1 Thanks for the report. I was able to reproduce the error on fedora 29 with pygit2 0.28.0 using the 2019.2.0 release of Salt. Testing with the current head of the 2019.2 branch, the issue appears to be fixed so this issue should be resolved once 2019.2.1 is released. I am in the process of tracking down the pull request that provided the fix.
FYI, the fix was here: https://github.com/saltstack/salt/pull/51304
For some reason, this pull request https://github.com/saltstack/salt/pull/51304 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 issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.
If this issue is closed prematurely, please leave a comment and we will gladly reopen the issue.
Thank you for updating this issue. It is no longer marked as stale.
@garethgreenaway can you look into this for sodium, please? removing fixed label to review in the release cycle, it maybe that this needs a port to master, perhaps?
closing as fixed in master and 3001RC
My first attempt was in this issue: https://github.com/saltstack/salt/issues/52319
It was closed because I used
example.com
to hide my own git server. wtf. I can reproduce the problem now. And I would like to help to get this fixed.pygit2 0.28.0
installed withpip
produces errors like that:This is my master config: (I set up a public repo to make sure that this is not a problem with a non-extisting server)
I see this on a debian system:
But also on a Fedora system:
If I install
python2-pygit2
from fedoras package repos everything works. It is version0.27.4