The EPEL 10 hackfest at Flock took place yesterday. We were able to get enough of the infrastructure working prior to the hackfest to enable packagers in attendance to do a controlled trial run building packages. This also resulted in a few branch request bugzillas for dependencies, which I realize in hindsight was confusing for packagers not at the hackfest. I apologize for not setting that expectation ahead of time.
Here is a summary of what is and isn’t working at this point.
What works:
- creating epel10 branches (
fedpkg request-branch epel10) - pushing commits to epel10 branches
- pull requests to epel10 branches
- Fedora CI scratch builds for epel10 pull requests
- creating epel10.0 builds from epel10 branches (
fedpkg buildfrom an epel10 branch) - automatic bodhi updates, similar to rawhide
What has not been completed yet:
- publish the epel/10 repo
- mirror the epel/10 repo
- create epel-release for epel10
- epel10 configs in mock-core-configs
- Fedora CI tasks for epel10 pull requests
- enable the testing period in bodhi
- epel10 versions in bugzilla
With no published repo, no mirroring, and no testing period (0 days to stable in bodhi), this is not a good time to start consuming EPEL 10. However, it is a good time for packagers to start building their packages. To be clear, this is the announcement to packagers that they can start building their packages. I’m hoping that in the next week or two we’ll be able to get the mock configs done to enable packagers to do local builds, but in the mean time koji scratch builds are a solid alternative.
We built about 70 packages during the allotted time of the hackfest, and as I write this we just passed 100 builds. Things seem to be working well. Please let me know if you notice any issues, aside from known items on the “not completed yet” list above.
Happy packaging!