Bug 2332462

Summary: build python-jsonpickle for epel10
Product: [Fedora] Fedora EPEL Reporter: Jonathan Wright <jonathan>
Component: python-jsonpickleAssignee: Gwyn Ciesla <gwync>
Status: CLOSED ERRATA QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: epel10CC: fedora, gwync, jonathan, romain.geissler
Target Milestone: ---   
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: python-jsonpickle-4.0.2-1.el10_1 Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2025-04-03 23:52:27 UTC 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:
Bug Depends On: 2332465, 2332468    
Bug Blocks: 2332461, 2336419    

Description Jonathan Wright 2024-12-15 10:54:31 UTC 
opening to track blockers
Comment 1 Romain Geissler 2025-04-02 08:53:55 UTC 
This can now build on EPEL 10 by using the rawhide branch content. See this scratch-build: https://koji.fedoraproject.org/koji/taskinfo?taskID=131005807
Comment 2 Fedora Update System 2025-04-02 15:39:25 UTC 
FEDORA-EPEL-2025-c4d7876f2e (python-jsonpickle-4.0.2-1.el10_1) has been submitted as an update to Fedora EPEL 10.1.
https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2025-c4d7876f2e
Comment 3 Fedora Update System 2025-04-03 03:27:18 UTC 
FEDORA-EPEL-2025-c4d7876f2e 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-c4d7876f2e

See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.
Comment 4 Fedora Update System 2025-04-03 23:52:27 UTC 
FEDORA-EPEL-2025-c4d7876f2e (python-jsonpickle-4.0.2-1.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.