On 30. 08. 19 18:25, Adam Williamson wrote:
Not. If you're getting it on an installed system that you're upgrading,
you probably need to manually switch the libgit2 module from the 0.27
stream to the 0.28 stream, that should clear it up.
I'm hit by this when trying to upgrade to F31:
Problém 2: problem with installed package
exa-0.8.0-13.module_f30+4041+ebfd9240.x86_64
- package exa-0.9.0-2.module_f31+5365+04413d87.x86_64 requires
libgit2.so.28()(64bit), but none of the providers can be installed
- exa-0.8.0-13.module_f30+4041+ebfd9240.x86_64 does not belong to a
distupgrade repository
- package libgit2-0.28.2-2.module_f31+5411+fa1856a4.x86_64 is excluded
- package exa-0.9.0-3.fc31.x86_64 is excluded
- package libgit2-0.28.2-3.fc31.x86_64 is excluded
I have never installed any module explicitly. As an user, I'm confused by this.
If this indeed requires my intervention, maybe we should document it as a common
bug? I had an impression that this was fixed via:
https://pagure.io/fesco/issue/2146
I've opened https://bugzilla.redhat.com/show_bug.cgi?id=1747408
Is this a candidate for a blocker?
--
Miro Hrončok
--
Phone: +420777974800
IRC: mhroncok
_______________________________________________
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org
Fedora Code of Conduct:
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives:
https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org
