#11904 Unretire epel8 branch for package Zim
Closed: Fixed by gui1ty. Opened by gui1ty.

The current maintainer of Zim retired all EPEL branches when taking over maintenance of the package. Recently, a bug was opened, requesting inclusion of Zim in EPEL9 and EPEL8.

I'm a co-maintainer of Zim and I volunteered maintaining the EPEL branches. The branch for EPEL9 was newly requested. However, epel8 already existed and was retired and dist-git doesn't allow me to merge my PR into it. I guess it needs to be unretired.

Please let me know if any additional information or steps are required.


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

Bugzilla ticket: https://bugzilla.redhat.com/show_bug.cgi?id=2257936

Metadata Update from @patrikp:
- Issue assigned to patrikp

Any progress on this?

I noticed the retirement commit was reverted a couple of days ago. Yet, the branch is still listed as inactive.

This should be sorted out now. :thumbsup:
https://src.fedoraproject.org/rpms/Zim/tree/epel8

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

It seems there's one last hurdle to be taken: BuildError: package Zim is blocked for tag epel8-testing-candidate.

https://koji.fedoraproject.org/koji/taskinfo?taskID=113492206

Metadata Update from @gui1ty:
- Issue status updated to: Open (was: Closed)

Ping? Any update?

Can you check now?

Relevant SOP: https://docs.fedoraproject.org/en-US/infra/releng_misc_guide/sop_unretire/#_unblock_the_package_in_koji

I checked the Koji tags via $ koji list-pkgs --show-blocked --package=Zim and the epel8 tag was blocked for some reason (I don't know why as I unblocked it previously). I unblocked it again (via $ koji unblock-pkg epel8 Zim).

Then I went to check Product Definition Center at this URL:
https://pdc.fedoraproject.org/rest_api/v1/component-branch-slas/?branch=epel8&global_component=Zim
And it shows the correct EOL of the branch as "2029-05-31" (I updated this previously, too).

As per the SOP that should be it.

Thank you! It's working now.

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

Metadata