fedmod defaults to generating modulemd files based on RPM's declared dependencies for the x86_64 architecture. This is due to a combination of x86_64 being the architecture that developers are most likely to be running locally, and the fact that arch-dependent module definitions aren't really specified yet (https://pagure.io/modulemd/blob/master/f/spec.yaml#_208 touches on the topic, but not in a way fedmod can really use at this point in time).
To fully support the dependency-reports use case (see https://pagure.io/modularity/fedmod/issue/35) fedmod will need to support resolving module dependencies for arbitrary architectures.
RFE. fedmod works for most of our requirements. dependency-report scripts are obsolete. The use case is where dependencies differ between architectures. Low priority, IMHO.
I assume this is fixed with @otaylor's dataset feature plus the configurability which has landed meanwhile.
Metadata Update from @nphilipp: - Issue close_status updated to: RESOLVED - Issue status updated to: Closed (was: Open)
Login to comment on this ticket.