#10445 set up epel9 external repo correctly
Closed: Fixed 2 years ago by mohanboddu. Opened 2 years ago by tdawson.

  • Describe the issue
    There was some miscommunication regarding the setup of the epel9 external repo. The intent was Plan C was for to use the CentOS Stream 9 AppStream, BaseOS and CRB repos. But the wording of the plan was bad and it could be interpreted in two different ways. As a result, the epel9 external repo was setup so that it is using the CentOS Stream 9 buildroot.

Please update the epel9 external repo so that it uses the CentOS Stream 9 AppStream, BaseOS and CRB repos only.

  • When do you need this? (YYYY/MM/DD)
    2021/12/10

  • When is this no longer needed or useful? (YYYY/MM/DD)
    2022/06/01

  • If we cannot complete your request, what is the impact?
    There will be an unknown amount of epel9 packages missing when RHEL9 is released.


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

2 years ago

@tdawson Does it still make sense to use cs9 buildroot for epel9 next? I think we should move both epel9 and epel9 next to use the cs9 shipped content. I know the current setup was needed initial setup, but I think its time that we should point both epel9 and epel9 next to use the CS9 shipped content. WDYT?

I agree with moving both epel9 and epel9-next to build off the shipped content.

I personally agree with them both being set to the shipped content. I also know that Neal would like that as well.

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

2 years ago

Log in to comment on this ticket.

Metadata
Boards 1
Ops Status: Backlog