@ppicka noticed that Modular repositories contain comps data https://dl.fedoraproject.org/pub/fedora/linux/releases/36/Modular/x86_64/os/repodata/df203c90b5e87cf5f7e2f7f32a9f8070d556acca5606a4fce8094045f73e3000-comps-Modular.x86_64.xml.
I think those data are duplicate of data in nonmodular Fedora repository and they could be removed from the Modular repository. Is that right, or is there any reason why the comps are placed along modules?
If they are not required there, could you please reconfigure Modular compose process not to include comps?
Metadata Update from @phsmoura: - Issue tagged with: medium-gain, medium-trouble, ops
CC: @lsedlar any thoughts here? Do we need to be adding comps to modular repos?
I think this is a bug in Pungi: it should be filtering the unused groups from the Modular variant (and all of them are unused). However, since the variant now configures a tag with modules instead of an explicit list, it does not work correctly.
Here's an issue for that: https://pagure.io/pungi/issue/1640
This should be fixed in pungi-4.3.6-2. The comps file will still be present, but will be empty. Builds are ready for Rawhide, 37 and 36. Updates:
Is this something that can wait until after freeze? Or should I seek a freeze break to update pungi?
V=C2=A0Mon, Nov 07, 2022 at 04:54:44PM +0000,=C2=A0Kevin Fenzi napsal(a):
Is this something that can wait until after freeze? Or should I seek a fr= eeze break to update pungi? =20 If the update contains only this one change, then it can wait.
Fixed some time ago closing.
Metadata Update from @humaton: - Issue close_status updated to: Fixed - Issue status updated to: Closed (was: Open)