The current generator only sets the content license for single packages as input, and the initial fix for https://pagure.io/modularity/fedmod/issue/28 will revert that so it is never set at all.
Either the generator needs to set this appropriately, or else we need to confirm that the Module Build System will fill this in as part of the build process, so we can ignore it from the perspective of the input file.
@ralph Does fm-orchestrator populate the content license fields based on the SRPMs that are actually built? If it does, then we can likely drop this capability at the fedmod level entirely.
@ralph Do you have an answer for Nick's question ? ^
I think the code for this should be in pungi -- if MBS did this, you could end up with licenses for packages that aren't part of the module in the end.
Yeah, this should be omitted from the input file; it must always be determined by the final output content. Users should not set this value and it should always be overwritten if it was.
Ok, this needs to be populated by pungi during a compose. Nothing to be done here afaik.
Metadata Update from @karsten: - Issue close_status updated to: CANCELLED - Issue status updated to: Closed (was: Open)
Login to comment on this ticket.