#11981 Retire kpipewire5 on f40 and rawhide
Closed: Fixed by churchyard. Opened by churchyard.

  • Describe the issue

kpipewire5 was retired in rawhide dist-git at 2024-01-04: https://src.fedoraproject.org/rpms/kpipewire5/c/d729bb799121577fdda187030bd853922bdc3b79?branch=rawhide

Nevertheless, it was branched for f40 and is active in both:

$ koji list-pkgs --show-blocked --tag f40 --quiet --package kpipewire5
kpipewire5              f40                                      orphan         
$ koji list-pkgs --show-blocked --tag f41 --quiet --package kpipewire5
kpipewire5              f41                                      orphan  

Please ensure proper retirement.

  • When do you need this? before f40 release

  • When is this no longer needed or useful? after f41 release

  • If we cannot complete your request, what is the impact? unmaintained package available in the repos

cc @ngompa


Metadata Update from @jnsamyak:
- Issue tagged with: low-gain, low-trouble, ops

Oh oof, yes please we need this not to be included in f40+ at all.

Okay, so I checked this issue and I saw a similar issue reported today at #11979 where it correctly had a retirement commit but it wasn't eol(ed) properly in the PDC branch and was not blocked in Koji as well, need to check why it happened;


To get this, I'll discuss this with @humaton and @kevin once if there is a proper way to do it already or I'll block this from Koji after having a quick discussion for both f40 and f41 via these, and use the adjest_eol script from releng

koji block-pkg f40 kpipewire5
koji block-pkg f41 kpipewire5

I checked the blocker_retired script, doesn't seem to find any issue there :/

FTR both https://pdc.fedoraproject.org/rest_api/v1/component-branches/?name=f40&global_component=kpipewire5 and https://pdc.fedoraproject.org/rest_api/v1/component-branches/?name=rawhide&global_component=kpipewire5 say the component is active.

Folks, this seems to be fixed now, can you please check, and let us know if there is anything else that is left?
CC: @churchyard

All good, thanks.

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

Metadata