Please branch and build python-pycurl for EPEL10 Reproducible: Always
Hello! python-pycurl is a package that was removed in RHEL 10 and is shipped in older RHEL releases. There is a small possibility that it will have to be added back to RHEL 10 after customer feedback. Therefore, I suggest to wait for a bit longer before branching for EPEL 10. Regards, Lukas
(In reply to Lukáš Zaoral from comment #1) > Hello! > python-pycurl is a package that was removed in RHEL 10 and is shipped in > older RHEL releases. > There is a small possibility that it will have to be added back to RHEL 10 > after customer feedback. > Therefore, I suggest to wait for a bit longer before branching for EPEL 10. As the requester, I can certainly wait for some time. However, is there any expected (even hand-waving) schedule for a decision on the inclusion into RHEL10? My (spongy) goal is for packages/applications that I support will be ready when RHEL10 is made available (2025H1?), and my stretch goal is to be able to start testing when C10S becomes available (2024Q4?). Thanks.
Hi, FYI, it is also a dependency of rpkg, which in term is needed for fedpkg/centpkg in EPEL 10 as well. Cheers, Romain
(In reply to Lukáš Zaoral from comment #1) > Hello! > python-pycurl is a package that was removed in RHEL 10 and is shipped in > older RHEL releases. > There is a small possibility that it will have to be added back to RHEL 10 > after customer feedback. > Therefore, I suggest to wait for a bit longer before branching for EPEL 10. > > Regards, > Lukas Hi, Almost 3 months after this initial message, what is the status here ? Will it be added back in CentOS 10 / RHEL 10 ?
Hello, my apologies for not replying sooner. So far no one has requested the package to be added back to CentOS Stream 10. However, RHEL 10 Beta was released less than two weeks ago so I'd like to wait a bit more for possible feedback. If nobody makes a request by Dec 8 2024, I'll branch the package for EPEL 10. Is this acceptable for you? Regards, Lukas
Fine for me, 8th of december is rather soon. However I would expect there are procedure to move packages from/to CentOS/EPEL no ? It's certainly not the first time this happens I guess.
(In reply to Romain Geissler from comment #6) > Fine for me, 8th of december is rather soon. However I would expect there > are procedure to move packages from/to CentOS/EPEL no ? It's certainly not > the first time this happens I guess. I am not the person you are directly asking, but I am aware that there is a process for removing packages from EPEL, including if Red Hat later decides to include it in a later update of a EL release, as orphaning can work in EPEL too, but, as I recall, it can be a bit convoluted in certain edge cases (different names, lower versions packaged by RH for the EL variant, EL customers semi-expecting long term (10+ year) availability, the EL variant only available in later versions of EL so orgs that have frozen to an earlier EL version may have to do extra work, etc.) such that if one can avoid having to deal with all of the extra steps and potentially cause difficulty for the EPEL/RH packagers and EL user community that is for the (much) better. As the original requester, while I do have other things that need python-pycurl, I understand that these things can take some time to get resolved, and I am glad to see the RH maintainer engaging in the request.
Hi, Was there any RHEL user who did raise the need to have this package on RHEL side ?
Hello, I've branched the package yesterday and I was able to build it today: https://koji.fedoraproject.org/koji/taskinfo?taskID=126673681 (I tried the build yesterday already but there was some delay before the package was put on the EPEL 10 allow-list in Koji.) Regards, Lukas
FEDORA-EPEL-2024-813211100c (python-pycurl-7.45.3-4.el10_0) has been submitted as an update to Fedora EPEL 10.0. https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2024-813211100c
FEDORA-EPEL-2024-813211100c (python-pycurl-7.45.3-4.el10_0) has been pushed to the Fedora EPEL 10.0 stable repository. If problem still persists, please make note of it in this bug report.