fedora-infrastructure

#11351 Retire cri-o module and go back to publishing cri-o and cri-tools as RPMs
Closed: Fixed by humaton. Opened by lorbus.

Closed: Fixed
Reopen Issue

I've already discussed this with the maintainer @haircommander . I will be taking up co-ownership of the cri-o and cri-tools RPMs as well.

Describe what you would like us to do:

Retire cri-o module and go back to publishing cri-o and cri-tools as RPMs

When do you need this to be done by? (YYYY/MM/DD)

ASAP

Requesting this ticket be moved to https://pagure.io/releng/issues

+1 in general though I'm not sure we should retire so early. I think this can be done for F39/cri-o 1.28.0 but we should leave the modules for a release or so

Ok, so granting admin access was done by the package's main admin.
It seems the module will be around for a little while. Once you get sorted out when we should retire the module @lorbus and @haircommander, can you please open the retirement request in the releng tracker?

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