Please branch and build python-setuptools-rust in epel10. If you do not wish to maintain python-setuptools-rust in epel10, or do not think you will be able to do this in a timely manner, I would be happy to be a co-maintainer of the package (FAS: music); please add me through https://src.fedoraproject.org/rpms/python-setuptools-rust/adduser
This is a dependency for maturin, which is needed to build various Python extensions that are written in Rust, such as Pydantic (python-pydantic-core).
The package is in c10s, https://gitlab.com/redhat/centos-stream/rpms/python-setuptools-rust . I'm not sure why you are unable to use it. Maybe it is still flagged as buildroot-only and therefore not included in CRB?
(In reply to Christian Heimes from comment #2) > The package is in c10s, > https://gitlab.com/redhat/centos-stream/rpms/python-setuptools-rust . I'm > not sure why you are unable to use it. Maybe it is still flagged as > buildroot-only and therefore not included in CRB? Yes, it’s a buildroot-only package (Buildroot level 1) in CentOS[1]. So is the dependency python-semantic_version[2]. These packages are only used for building CentOS/RHEL packages, and aren’t shipped in any publicly available repositories, so they’re still eligible for EPEL – no machine should ever see buildroot-only packages and EPEL packages at the same time. [1] https://tiny.distro.builders/view-rpm--view-c10s--python3-setuptools-rust.html [2] https://tiny.distro.builders/view-rpm--view-c10s--python3-semantic_version.html
Here’s a link about EPEL eligibility: https://docs.fedoraproject.org/en-US/epel/epel-policy/#_policy That said, if python-semantic_version and python-setuptools-rust were added to CRB rather than built in EPEL, that would be equally satisfactory, and probably easier if the same person/people would be maintaining the packages in both cases.
Let me to to Trivino. He took over stream and RHEL package maintenance from me. If he agrees to move the components from buildroot to CRB, then I would prefer that solution.
If you do, please put them to a CRB workload in https://github.com/minimization/content-resolver-input so this does not happen again with CentOS Stream 11.
Good point, Miro! Ben, it might take a while. Carl sent me a information how to request buildroot -> CRB move. The move has to go through an approval process. I'll keep you posted.
(In reply to Christian Heimes from comment #8) > Good point, Miro! > > Ben, it might take a while. Carl sent me a information how to request > buildroot -> CRB move. The move has to go through an approval process. I'll > keep you posted. While I know that people are going to be asking for Pydantic in particular as we approach the RHEL 10 release, I’m not on any kind of strict timeline. I’m happy to wait for the approach that is best for you in the long term. Thank you for the follow-up, and for working on this!
*** Bug 2323780 has been marked as a duplicate of this bug. ***
Hi, could you share the Jira link(s) here?
*** Bug 2324165 has been marked as a duplicate of this bug. ***
I just realized that there is an outstanding request to add this package to EPEL 9 as well (bug 2173215). There was some discussion in that bug of the package moving from the CentOS/RHEL 9 buildroot to CRB, but it seems to have stalled out. Is this request for 10 headed toward the same fate? Since no subpackages are shipped in BaseOS, AppStream, or CRB, this package is eligible for EPEL, but it would be easier for everyone if the packages that are already built could just be shipped in CRB.
I realized that while we have discussed moving this to CRB to avoid duplicating the work in EPEL, we haven't yet formally requested it. I've done that in this issue. https://issues.redhat.com/browse/RHEL-66224
Hi Carl, thanks for filing the RHEL ticket. I also filed the one for python3-semantic_version. We need both in the CRB, and I’ll be working on them. Hopefully, they won’t get stuck. https://issues.redhat.com/browse/RHEL-66994 (In reply to Carl George 🤠 from comment #18) > I realized that while we have discussed moving this to CRB to avoid > duplicating the work in EPEL, we haven't yet formally requested it. I've > done that in this issue. > > https://issues.redhat.com/browse/RHEL-66224
Right now it seems that: - Both python3-semantic_version & python-setuptools-rust (recent versions) are available in CRB - There is still some thing to clarify with python3-semantic_version being duplicated in two repos: CRB & EPEL 10 - python-brycrpt no longer has problems wrt python-setuptools-rust when trying to build it on EPEL 10 (but misses now some rust dependencies). So I guess this ticket can be closed ?