Bug 2319899

Summary: Please branch and build python-fasjson-client for EPEL 10
Product: [Fedora] Fedora EPEL Reporter: Xavier Bachelot <xavier>
Component: python-fasjson-clientAssignee: Carl George 🎩 <carl>
Status: CLOSED ERRATA QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: epel10CC: carl, extras-orphan, farrotin, infra-sig, kevin
Target Milestone: ---   
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: python-fasjson-client-1.1.0-4.el10_1 Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2025-06-08 00:30:07 UTC Type: ---
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: 2322956, 2364268    
Bug Blocks: 2303880, 2313905    

Description Xavier Bachelot 2024-10-19 10:04:22 UTC
Hi,

Could you please branch and build python-fasjson-client for EPEL 10 ?
It is needed to build another package.

Regards,
Xavier

Comment 1 Xavier Bachelot 2025-05-05 08:59:27 UTC
*** Bug 2345485 has been marked as a duplicate of this bug. ***

Comment 2 Fedora Update System 2025-05-30 08:00:48 UTC
FEDORA-EPEL-2025-6e520af8a6 (fasjson-client for epel10) has been submitted as an update to Fedora EPEL 10.1.
https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2025-6e520af8a6

Comment 3 Fedora Update System 2025-05-31 01:41:00 UTC
FEDORA-EPEL-2025-6e520af8a6 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-6e520af8a6

See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.

Comment 4 Fedora Update System 2025-06-08 00:30:07 UTC
FEDORA-EPEL-2025-6e520af8a6 (fasjson-client for epel10) has been pushed to the Fedora EPEL 10.1 stable repository.
If problem still persists, please make note of it in this bug report.