Bug 2032543

Summary: [RFE:EPEL9] EPEL9 branch for python-celery
Product: [Fedora] Fedora EPEL Reporter: Pat Riehecky <riehecky>
Component: python-celeryAssignee: Matthias Runge <mrunge>
Status: NEW --- QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: epel9CC: andrew, aurelien, furlongm, fzatlouk, jpopelka, mrunge, ngompa13, pingou
Target Milestone: ---   
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:

Description Pat Riehecky 2021-12-14 17:01:48 UTC
Description of problem:

Can python-celery be branched for EPEL9

Version-Release number of selected component (if applicable): current fedora


How reproducible:


Steps to Reproduce:
1.
2.
3.

Actual results:


Expected results:


Additional info:

Comment 1 Pat Riehecky 2022-01-28 20:01:56 UTC
Will you be able to branch and build python-celery in epel9?

Comment 2 Matthias Runge 2023-08-25 06:44:00 UTC
Sorry, I completely missed this.
I have no plans nor the time to work on any epel related stuff, and I would be more than happy to get out of the way and to hand this over to someone who has the time to work on it.

Comment 3 Jiri Popelka 2023-08-28 12:45:32 UTC
If anyone's interested, I created a Copr repo with EPEL9 rebuild of celery and its missing transitive (build) dependencies.
I chose to build everything from dist-git f36 branches, which contains celery 5.2.6 because the newer 5.3.* needs click>=8.1.2 (there's 8.0.3 in epel9) and python-dateutil>=2.8.2 (there's 2.8.1 in rhel9).

Comment 4 Jiri Popelka 2023-08-28 12:46:01 UTC
damn, the link:
https://copr.fedorainfracloud.org/coprs/jpopelka/celery

Comment 5 Matthias Runge 2023-10-20 13:20:20 UTC
*** Bug 2245193 has been marked as a duplicate of this bug. ***