#10463 Untag python-filelock-3.3.1-1.el9.next and python-distlib-0.3.2-1.el9.next from EPEL 9 Next
Closed: Fixed by humaton. Opened by churchyard.

  • Describe the issue

I've built python-filelock-3.3.1-1.el9.next and python-distlib-0.3.2-1.el9.next in EPEL 9 Next before the plan of EPEL 9 was changed. Now I've also built python-filelock-3.3.1-1.el9 and python-distlib-0.3.2-1.el9 from the same commit in regular EPEL 9. The EPEL 9 Next builds have a higher release but provide no benefit for the users. Could you please untag them from EPEL 9 Next?

Thanks

  • When do you need this? Any time

  • When is this no longer needed or useful? It will be always useful

  • If we cannot complete your request, what is the impact? Minor difference between EPEL 9 and EPEL 9 Next content that is not needed.


Untaged

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

Thank you.

Metadata