Hi, Please branch and build python-starlette in epel10. Trying right now with the rawhide branch content, I get this error: error: line 35: Unknown tag: BuildSystem: pyproject If I revert this commit: https://src.fedoraproject.org/rpms/python-starlette/c/ed8e477e8b9ba85e424deefaf033916600f777c5?branch=rawhide then it goes further, we have a dependency on python-trio. However I am not sure reverting this commit is the right thing to do. Shall this "BuildSystem" tag support be backported to EPEL 10 instead ? Reproducible: Always
(In reply to Romain Geissler from comment #0) > […] I am not > sure reverting this commit is the right thing to do. Shall this > "BuildSystem" tag support be backported to EPEL 10 instead ? That would require a newer version of rpm itself, which I wouldn’t expect to happen. I would expect to revert the migration to the declarative buildsystem in a potential EPEL10 branch, like this: https://src.fedoraproject.org/fork/music/rpms/python-starlette/tree/epel10test I don’t necessarily object to bringing Starlette to EPEL10, but I question whether it makes sense to do it solely for building documentation: https://bugzilla.redhat.com/show_bug.cgi?id=2335575#c1 In addition to python-trio, this would require python-anyio and python-httpx.
This bug appears to have been reported against 'rawhide' during the Fedora Linux 42 development cycle. Changing version to 42.
FEDORA-EPEL-2025-7400e0aa88 (python-starlette-0.46.0-16.el10_1) has been submitted as an update to Fedora EPEL 10.1. https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2025-7400e0aa88
FEDORA-EPEL-2025-7400e0aa88 has been pushed to the Fedora EPEL 10.1 testing repository. You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2025-7400e0aa88 See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.
FEDORA-EPEL-2025-7400e0aa88 (python-starlette-0.46.0-16.el10_1) has been pushed to the Fedora EPEL 10.1 stable repository. If problem still persists, please make note of it in this bug report.