Created attachment 1948537 [details] python-openapi-core.spec Please branch and build python-openapi-core in epel9. Unfortunately the versions in Fedora are too new, because it requires python3-openapi-schema-validator < 0.3 and python3-openapi-spec-validator < 0.5. For this reason I propose the attached spec file with the latest version suitable for EPEL 9 - based on your spec file in Rawhide.
Created attachment 1948538 [details] python-openapi-core-0.14.5-pathable.patch
Thanks for taking the time to work out the details and offer spec files. Martin, do you want to co-maintain any of these packages? And if so, Mattia, do you want Martin as a co-maintainer for openapi-spec-validator and openapi-core? Mattia, do you have any thoughts? If you are happy too then I can request the EPEL9 branches and start building.
Thank you for responding so quickly! First I would want to let you know, that I am not a Fedora packaging-maintainer and second my packaging experience is limited.
I prepared the following, incorporating Martin’s choice of versions and suggested patches: https://src.fedoraproject.org/fork/music/rpms/python-openapi-schema-validator/blob/epel9test/f/python-openapi-schema-validator.spec https://src.fedoraproject.org/fork/music/rpms/python-openapi-spec-validator/blob/epel9test/f/python-openapi-spec-validator.spec https://src.fedoraproject.org/fork/music/rpms/python-openapi-core/blob/epel9test/f/python-openapi-core.spec These built successfully in COPR: https://copr.fedorainfracloud.org/coprs/music/openapi-epel9/packages/ @mattia.verga, when you have a chance, could you take a look at the above and make sure you are happy?
I'm not enthusiastic about maintaining packages for EPEL, mainly because there are always troubles about outdated dependencies and also because there's no way of knowing what package is already available in the main RHEL repositories (at least, I never found a way to). In this case, since you've already done all the research and packaging work, I have no objections if you (@Ben) want to proceed in deployment. I'm quite busy right now and cannot guarantee to have enough time to do that in a foreseeable future. @Martin, if you manage to be sponsored as package maintainer I'd be happy to give you the maintainership of EPEL branch(es) of openapi-spec-validator and openapi-core.
Fair enough! I’ll go ahead, then. Martin, please let me know if you want to take the time to co-maintain these packages or contribute to Fedora and EPEL packaging in other ways. I can sponsor you into the packager group and answer questions, help you get started, and do the general mentoring activities expected of a sponsor. Mattia, you can feel free to make me the EPEL bugzilla assignee for these packages for now. As a general note, the stable nature of the RHEL distribution, and the fact that we are already at the latest versions we are able to package for EPEL9, means that these packages will probably be mostly “frozen in time” at the versions in the COPR for the life of EPEL9. EPEL maintenance will mostly mean fixing anything that breaks, backporting serious bug or security fixes when they are pointed out and it is possible to fix them, and retiring the package in the unlikely event that it becomes impossible to keep it usable. It’s hard to predict whether these packages will need to be touched several times or not at all in the life of EPEL9.
FEDORA-EPEL-2023-2168f99689 has been submitted as an update to Fedora EPEL 9. https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2023-2168f99689
FEDORA-EPEL-2023-2168f99689 has been pushed to the Fedora EPEL 9 testing repository. You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2023-2168f99689 See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.
I am still recovering from sickness, please give me a few more days. Thank you for pushing the packages to testing!
FEDORA-EPEL-2023-2168f99689 has been pushed to the Fedora EPEL 9 stable repository. If problem still persists, please make note of it in this bug report.