#8616 Block perl-bootstrap modules from entering composes
Closed: Fixed by humaton. Opened by ppisar.

  • 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.

https://pagure.io/pungi/issue/1260

The upstream issue is fixed and in pungi we are using. Can someone propose a PR with the desired 'filter_modules' ?

Hi, since upstream has implemented filter_modules. Can you please propose PR to pungi-fedora with the desired effect?

https://pagure.io/pungi-fedora/pull-request/982 should fix this.

I have not included rust:* as we think its not needed with the https://fedoraproject.org/wiki/Changes/Rust_Crate_Packages_For_Release_Branches change.

Could you please also exclude perl-YAML-bootstrap:*?

In https://pagure.io/pungi-fedora/pull-request/982 we blocked perl-bootstrap and rpm

@ppisar could we just change that to 'perlbootstrap' or would that catch something we don't want?

'perl*bootstrap*' is fine.

https://pagure.io/pungi-fedora/pull-request/998

the PR is now merged closing this issue.

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

Metadata