The currently module metadata reading code assumes that any given RPM will appear in the artifact listing for at most one module.
This is not right, so fedmod should instead note that a particular resolution is ambiguous, and either ask a human to deal with it, or else try to come up with a decision based on depending on as few distinct modules as possible, or (failing that), depending on whichever module is smaller (that may not be the best heuristic, but it weighs against big modules like bootstrap and installer).
Making some initial implementation notes:
At that level, the simplest fix will be to upgrade the reverse lookup entry from a single string to a set when the RPM or SRPM is found in multiple modules.
That will make the extra metadata available for the dependency-reports use case in https://pagure.io/modularity/fedmod/issue/35
The modulemd generation use case can then be updated to use the heuristic described in the issue report.
@asamalik added an initial version of this to handle the new repoquery-style subcommands - the remaining step now is to fix the other commands to use that metadata, so we can drop the old-style ambiguous metadata entirely.
PR: https://pagure.io/modularity/fedmod/pull-request/56
Metadata Update from @ncoghlan: - Issue assigned to ncoghlan
Metadata Update from @ncoghlan: - Issue close_status updated to: RESOLVED - Issue status updated to: Closed (was: Open)
Login to comment on this ticket.