releng

#10474 Make epel9 and epel9-next retirement work
Closed: Fixed by humaton. Opened by churchyard.

Closed: Fixed
Reopen Issue
  • Describe the issue

I think that pushing a retirement commit to epel9 or epel9-next won't actually block the package.

Looking at https://pagure.io/releng/blob/main/f/scripts/block_retired.py I believe it needs to be added in RETIRING_BRANCHES and PROD_ONLY_BRANCHES and I can do that, but there is also self.mapping which I am not quite sure I understand.

  • When do you need this? soon

  • When is this no longer needed or useful? On EPEL 9 EOL.

  • If we cannot complete your request, what is the impact? Packages retired from EPEL 9 will not actually be retired. See e.g. https://src.fedoraproject.org/rpms/python-mock/commits/epel9

Hi, @churchyard

here is PR with corresponding changes. https://pagure.io/releng/pull-request/10518

Thanks for merging it. Could you please also block/retire python-mock on epel9? https://src.fedoraproject.org/rpms/python-mock/commits/epel9
Edited by churchyard

Done

$ koji list-pkgs --show-blocked --package python-mock --tag=epel9
Package                 Tag                     Extra Arches     Owner          
----------------------- ----------------------- ---------------- ---------------
python-mock             epel9                                    churchyard      [BLOCKED]

https://pdc.fedoraproject.org/rest_api/v1/component-branches/?type=rpm&global_component=python-mock

Metadata Update from @humaton:
- Issue close_status updated to: Fixed
- Issue status updated to: Closed (was: Open)
Metadata
None
None
None
None
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.