-
Notifications
You must be signed in to change notification settings - Fork 231
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Building mock on CentOS 10 has missing python RPMS #1392
Comments
I've published a working repo to build mock on CentOS Stream 10, at https://github.com/nkadel/mockrepo . I'm lying a bit to those configs, and generally building with AlmaLinux now, but with the AlmaLinux file replaced with the CentOS Stream 10 configs I've published at https://github.com/nkadel/nkadel-mock/ , it works well. I've had difficulty publishing to EPEL before, the registration process got pretty confusing. Anyone is welcome to grab and review these for updates to EPEL. I do tend to roll back my RPM release numbers to "0.1" instead of the "1" used by EPEL, so I automatically get the EPEL versions when they're published. |
Thank you for opening the issue, but this doesn't seem to be fixable in Mock. We should wait till the EPEL 10 appears, and then add a new set of configuration files. |
Agreed. It's a heads up on the problem. I've gone ahead and added them to https://github.com/nkadel/mockrepo/ , which requires a bootstrap build to initially enable the initial copy of mock itself. |
Short description of the problem
Building mock on CentOS 10 has missing python RPMS
Output of
rpm -q mock
Not applicable
Any additional notes
Missing RPMs for compilation on CentOS 10 include:
Those are all EPEL published RPMs. I could, in theory, spend some time adding them individually to my https://github.com/nkadel/mockrepo/ for building test builds of mock, but I figure you folks might get more traction than me getting the EPEL 10 repos available for use by "mock" on CentOS 10. And if our friends at EPEL are going to use mock to build RPMs, here is a starting list of missing requirements.
The text was updated successfully, but these errors were encountered: