On 6/14/19 6:29 AM, Daniel Mach wrote:
Dne 14. 06. 19 v 6:23 Samuel Sieb napsal(a):
After reading the bug report and the discussions, I still don't
understand why dnf is complaining about a conflict with packages
(modules?) that are not installed and are not even trying to be
installed. Can someone explain that?
The dependency resolution is done on 2 levels.
RPM dependency resolution still works the same even with modules.
What's different on a modular system is a pre-processing step that
resolves modules and filters out RPMs that do not match with
enabled/default streams.
What makes it even more complicated is stream expansion:
https://docs.fedoraproject.org/en-US/modularity/architecture/stream-expansion/
Some modules get build several times against multiple dependency sets.
These dependency sets are captured as Context field in module metadata.
DNF has to resolve the contexts and pick the right ones based on enabled
streams. This is done for *every* module version (not just the latest)
in order to compute which RPMs will be available to the user and which
not. And this causes the conflicts you were asking about.
But I still don't understand why it's looking at modules that are not
installed and not asked to be installed. If they aren't getting
installed, how is there a conflict? This seems to eliminate a lot of
the benefit of modules.
_______________________________________________
devel mailing list -- devel@xxxxxxxxxxxxxxxxxxxxxxx
To unsubscribe send an email to devel-leave@xxxxxxxxxxxxxxxxxxxxxxx
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@xxxxxxxxxxxxxxxxxxxxxxx
