Currently, when a maintainer requests an epel8 branch, they also get an epel8-playground branch, and a package.cfg file is put in their epel8 branch. We (the EPEL Steering Committee) have agreed on a new vision for EPEL8 Playground, that doesn't include automatic building of all epel8 packages. Please remove the step that adds package.cfg to the epel8 branch.
So, when a maintainer requests an epel8 branch, they also get an epel8-playground branch, but that's it. No package.cfg is added to either branch.
2020/09/22
This is likely a patch to https://pagure.io/fedscm-admin to not add this file.
This will require dev work and release. No promises on our side to have this done by next week.
OK, I didn't know the work process for this, I was hoping it would have been simpler. Do I need a separate issue or bug for this? Or is this issue sufficient?
https://pagure.io/fedscm-admin/issue/48
Metadata Update from @mohanboddu: - Issue close_status updated to: Upstream - Issue status updated to: Closed (was: Open)
Metadata Update from @mohanboddu: - Issue status updated to: Open (was: Closed)
Metadata Update from @mohanboddu: - Issue assigned to humaton - Issue priority set to: Waiting on Assignee (was: Needs Review) - Issue tagged with: dev, medium-gain, medium-trouble
https://pagure.io/fedscm-admin/pull-request/49
There is a stable build for f32,f33, and rawhide. Once people update to the latest release all newly processed epel8 requests will not include the package.cfg
Metadata Update from @humaton: - Issue close_status updated to: Fixed - Issue status updated to: Closed (was: Open)
Login to comment on this ticket.