Learn more about these different git repos.
Other Git URLs
Describe the issue
perl-bootstrap modules should live in MBS and Koji only. They are not intended for end users and thus adding them to the composes is confusing. If possible, block them from going into any (Rawhide, F31, and F30) composes. But do not block them in MBS and Koji. We need them for building perl modules and also we update them from time to time.
When do you need this?
Before branching F31.
If we cannot complete your request, what is the impact?
There will be unsupported modules in Fedora composes. If having build-only modules is not possible, I'm fine with that. But this does not deliver a good user experience.
Metadata Update from @mohanboddu:
- Issue tagged with: meeting
Same for rpm:*, rust:* modules.
The upstream issue is fixed and in pungi we are using. Can someone propose a PR with the desired 'filter_modules' ?
to comment on this ticket.