#7924 Whitelist "-devel" modules in fxx-modular-updates-candidate tags
Closed: It's all good 5 years ago Opened 5 years ago by mprahl.

  • Describe the issue

The Modularity Working Group has requested that MBS provide "-devel" modules which are modules that contain all the filtered out RPMs from that module that would be shipped.

I can't find a ticket requesting this, but it was implemented in this PR:
https://pagure.io/fm-orchestrator/pull-request/1062

MBS in stage (not deployed in production) currently fails because the Koji content generator build for the "-devel" module (e.g. "testmodule-devel") is not whitelisted in the fxx-modular-updates-candidate tags. Could you please take the current list of modules we whitelist and also whitelist their "-devel" counterparts?

I'm tagging @sgallagh @psabata @jkaluza to provide context here if needed.

  • When do you need this? (YYYY/MM/DD)

By November 30th, but earlier would be appreciated.

  • When is this no longer needed or useful? (YYYY/MM/DD)

N/A

  • If we cannot complete your request, what is the impact?

We cannot provide the "-devel" modules the the Modularity Working Group requested and we would need to add code in MBS to make this configurable.


The feature exists to simplify local modular package development but if it's going to be available in Fedora, we should figure out how to ship this.

I'd rather not see these pollute the module list output for everyone, so maybe let's make them available in a separate repo, if at all.

Metadata Update from @mohanboddu:
- Issue tagged with: meeting

5 years ago

Metadata Update from @mprahl:
- Issue close_status updated to: It's all good
- Issue status updated to: Closed (was: Open)

5 years ago

Login to comment on this ticket.

Metadata