koji

#4262 How to generate the * module.yaml.gz file under the repodata of a module
Closed: Invalid by mikem. Opened by houlifei.

Closed: Invalid
Reopen Issue

Hello,I have imported the metadata of the module package through Koji import cg. Whether it is Kojira or my manual regen repo, it will not generate the * module.yaml.gz file, for example: Koji regen repo -- nowait module-python36-3.6-2020212919105436-fa808afa-build. I have checked the normal module compilation process and found that newrepo is done by MBS themselves. Is the method I generated incorrect? Please advise on the correct generation method. Thank you very much.

Please keep in mind that this is an issue tracker, not a support system. The correct place to ask questions is either the mailing list or the Element/Matrix room. Please do not open issues simply to ask a question.

Metadata Update from @mikem:
- Custom field Size adjusted to None

Koji doesn't really have direct support for modularity. The MBS system uses koji to build modules. MBS imports module metadata into Koji, but Koji doesn't do anything special with it. Koji's repo mechanism is not designed to handle module metadata, just rpms.

At this point I would advise against relying on modularity. Fedora has abandoned it.

https://fedoraproject.org/wiki/Changes/RetireModularity

Metadata Update from @mikem:
- Issue close_status updated to: Invalid
- Issue status updated to: Closed (was: Open)

This issue has been migrated to Fedora Forge:
https://forge.fedoraproject.org/koji/koji/issues/4262

Please continue any further discussion there.
Metadata
None
None
None
None
Low
None
Static archive. pagure.io was sunset in 2026; this is a read-only snapshot.
Red Hat Logo

Fedora is sponsored by Red Hat. Learn more about the relationship between Red Hat and Fedora »

© Red Hat, Inc. and others.