#10144 Unretire rpms/cri-o
Closed: Get back later 22 days ago by mohanboddu. Opened 2 months ago by haircommander.

  • Describe the issue
    I don't know why it was retired but it is active
  • When do you need this? (YYYY/MM/DD)
    as soon as possible
  • When is this no longer needed or useful? (YYYY/MM/DD)
    we have no intention of stopping building cri-o on fedora
  • If we cannot complete your request, what is the impact?
    we will have to package fedora in a different way

we will have to package fedora in a different way

:astonished:

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

2 months ago

I think it was retired because it is a module. It was orphaned and retired in Fedora 29/30 timeframe.

Unretiring this package would make it possible to build the un-modular version.. the modular version of this package is done via different directory tree.

ohh thanks for the context.

I probably should revisit my cri-o update docs. I previously thought I was supposed to push to the main repo, and then update the module repo to update the module. That must be out of date or wrong now. sorry for the noise

Metadata Update from @haircommander:
- Issue close_status updated to: It's all good
- Issue status updated to: Closed (was: Open)

2 months ago

No I forgot that Fedora does not allow modular only packages. Your request was corect.

it was in fact not all good

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

2 months ago

@haircommander so the package is retired for more than 8 weeks actually 2 years now. We will require a re-review request to unretire the package in rawhide.

@haircommander Please reopen this ticket when the review is approved.

Thanks.

Metadata Update from @mohanboddu:
- Issue close_status updated to: Get back later
- Issue status updated to: Closed (was: Open)

22 days ago

Login to comment on this ticket.

Metadata
Boards 1
Ops Status: Backlog