On Sun, Jun 16, 2019 at 7:15 AM Kevin Kofler kevin.kofler@chello.at wrote:
Adam Samalik wrote:
So, I'd like to discuss the libgit issue [1] [2] we're experiencing. With a help of a few people, I've put together this post to get us on common ground: https://communityblog.fedoraproject.org/modularity-vs-libgit/
There are few ideas about solving the issue right now. But we might be able to think about better ways to deal with similar issues long-term. Let's do this!
[1] https://bugzilla.redhat.com/show_bug.cgi?id=1717117 [2] https://pagure.io/fesco/issue/2146#comment-575852
As I had posted in a blog comment:
This is exactly the dependency hell (different packages/modules depending on incompatible versions of the same module) that I had been warning about ever since modularity has first been discussed in Fedora. I pointed out from day one that this is a showstopper that makes modularity entirely impractical and unsupportable. My concerns were dismissed or ignored. Now you are seeing exactly the situation that I had been warning about from day one.
Kevin Kofler
As best I can tell, most of the dependency nightmares in Fedora and RHEL 8 can be resolved, *so far*, by disabling the insistence on "best" matching in mock. I ran into the modular component dependency mismatches, hard, when backporting Samba 4.10.4 to RHEL 8. I'm not sure how broken this is going to be for actually deploying RPMs.