Learn more about these different git repos.
Other Git URLs
If I have a module that requires another module, I can't seem to add packages from that module to the "downstream" profile.
For example, my-cool-db-visualizer depends on the postgresql-client (psql) being installed. Even if i have the postgresql module required by my-cool-db-visualizer, if I add "postgresql" to the rpms section of my "default" profile, I get an error like the one below when I try to install it.
Should this work?
Last metadata expiration check: 0:00:44 ago on Sun 05 May 2019 01:58:23 PM EDT. Unable to resolve argument my-cool-db-visualizer:1/default No match for package postgresql Error: Problems in request: broken groups or modules: my-cool-db-visualizer:1/default
Yes, this is expected to work. The profile content to install is expected to be determined once the modules and their dependent modules are enabled.
This is part of the original spec; we used the example of 389 DS as representative. The 389ds module would provide all of the content, but the Red Hat DS and FreeIPA modules would list it in their profiles.
OK, good, it seemed weird. Probably need to file a bug against dnf.
So, turns out, this is a "Virtual Provides" problem. I was using "python3" and the actual rpm is called "python36." Ugh.
Metadata Update from @langdon: - Issue close_status updated to: Invalid - Issue status updated to: Closed (was: Open)
Login to comment on this ticket.