Bug 2048599

Summary: [RFE:EPEL9] branch python-u-msgpack-python
Product: [Fedora] Fedora Reporter: Steve Traylen <steve.traylen>
Component: python-u-msgpack-pythonAssignee: Steve Traylen <steve.traylen>
Status: CLOSED ERRATA QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: rawhideCC: mhroncok, python-sig
Target Milestone: ---   
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: python-u-msgpack-python-2.7.1-5.el9 Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2022-02-16 01:54:14 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:    
Bug Blocks: 2048594    

Description Steve Traylen 2022-01-31 15:18:44 UTC
Please can python-u-msgpack-python be branched and made available for EPEL9.

I have confirmed the current python-u-msgpack-python-2.7.1-4.fc36.src.rpm 
does build and install into centos-stream-9-mock.

I can co maintian the epel package if you like?

Steve.

Comment 1 Miro HronĨok 2022-01-31 15:42:12 UTC
You are now the EPEL maintainer of python-u-msgpack-python.

Comment 2 Fedora Update System 2022-02-07 07:29:08 UTC
FEDORA-EPEL-2022-05b8ca7ce4 has been submitted as an update to Fedora EPEL 9. https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2022-05b8ca7ce4

Comment 3 Fedora Update System 2022-02-08 02:13:49 UTC
FEDORA-EPEL-2022-05b8ca7ce4 has been pushed to the Fedora EPEL 9 testing repository.

You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2022-05b8ca7ce4

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

Comment 4 Fedora Update System 2022-02-16 01:54:14 UTC
FEDORA-EPEL-2022-05b8ca7ce4 has been pushed to the Fedora EPEL 9 stable repository.
If problem still persists, please make note of it in this bug report.