I'm unable to submit a module build:
$ fedpkg module-build --watch Submitting the module build... Could not execute module_build: The build failed with: The stream "7.2" that is stored in the modulemd does not match the branch "epel-8-php-7.2"
I don't understand why this have to match, this constraint seems bad
A stream may be different per distribution / version
Especially, EPEL branches may have different content than Fedora ones And EPEL-8 may also be different than EPEL-9, especially for module extending base ones, with different content. And also because stuuf available in base distribution.
For now, I will request the 7.2 and 7.3 branch, but this is only a workaround, I really think this issue is a major blocker.
Can you let us know what module you are building, so we have an example of the yaml file you are using.
module is "php-extras" https://src.fedoraproject.org/modules/php-extras/blob/7.2/f/php-extras.yaml
Is this possible to do in Fedora? Or is this just an EPEL bug? I also don't consider this a blocker, just a bug.
Metadata Update from @smooge: - Issue priority set to: Waiting on Assignee (was: Needs Review) - Issue tagged with: releng
Metadata Update from @smooge: - Issue tagged with: mbs
at a glance, looks like configuration can allow this.
if mmd.get_stream_name() and mmd.get_stream_name() != scm.branch: if not conf.allow_stream_override_from_scm: raise ValidationError( 'The stream "{0}" that is stored in the modulemd does not match the branch "{1}"' .format(mmd.get_stream_name(), scm.branch) )
What is your allow_stream_override_from_scm setting?
FTR:
$ git grep allow_stream_override_from_scm
in the ansible repo, does not return anything.
Should this be forwarded to another issue tracker?
Filed a MBS ticket - https://pagure.io/fm-orchestrator/issue/1624
Closing this ticket since it's tracked upstream
Metadata Update from @pingou: - Issue close_status updated to: Upstream - Issue status updated to: Closed (was: Open)