Hi, Please branch and build rust-itertools0.11 in epel10. It is a dependency of python-libcst. Cheers, Romain
It would likely be better to bump the itertools dependency from 0.11 to 0.12 in python-libcst before importing it to EPEL 10. We try to limit the number of "compat" packages (for older versions of Rust crates) that we import into EPEL 10, since they increase maintenance burden in the long term.
(leaving open for now until this is addressed)
If I upgrade libcst to the latest sources (but I can't even submit that as a pull request as I am not a packager yet), the number of missing dependencies when build libcst in EPEL 10 is reduced to: Problem 1: nothing provides requested (crate(peg/default) >= 0.8.4 with crate(peg/default) < 0.9.0~) Problem 2: nothing provides requested (crate(pyo3/default) >= 0.20.0 with crate(pyo3/default) < 0.21.0~) Problem 3: nothing provides requested (crate(pyo3/extension-module) >= 0.20.0 with crate(pyo3/extension-module) < 0.21.0~) peg 0.8 is already the "latest" version, so here just asking for an EPEL 10 branching should be enough. For pyo3, it seems the latest upstream version is 0.23. However I did find this dependabot pull request upstream https://github.com/Instagram/LibCST/pull/1259 where the CI lots of failure, so I assume libcst is not ready for the upgrade just yet. So would it be ok to branch just rust-pyo30.20 for EPEL 10 ?
Note: there is also this pull request (still not merged for now) to upgrade to pyo3 0.22: https://github.com/Instagram/LibCST/pull/1180
I'm slightly confused what you're trying to do here - what I suggested in Comment 1 was to patch the *current* version of python-libcst to build with itertools 0.12 instead of 0.12. The fact that it pulls in outdated versions of pyo3 is a different problem.
Ok, I would naively thought it was more logical to upgrade libcst sources (which indirectly also upgrades the itertools dependency version) than backporting in an old libcst an upstream upstream upgrade of itertools. Both fix the issue though, and I have just submitted this which works both in rawhide and EPEL 10 (EPEL still lacks the above mentionned rust dependencies): https://src.fedoraproject.org/rpms/python-libcst/pull-request/6 So if this pull request is merged, this ticket can be closed as "WONT FIX".
Thanks, the PR looks good to me. Knowing the maintainers of python-libcst (they are both also Rust SIG members), I assume the PR will get merged.