Bug 2540858

Summary:	Please branch and build python-wsproto in epel9
Product:	[Fedora] Fedora EPEL	Reporter:	Ben Beasley <code>
Component:	python-wsproto	Assignee:	Carl George 🤠 <carlwgeorge>
Status:	CLOSED ERRATA	QA Contact:
Severity:	unspecified	Docs Contact:
Priority:	unspecified
Version:	epel9	CC:	carlwgeorge, python-packagers-sig
Target Milestone:	---
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:	python-wsproto-1.2.0-9.el9	Doc Type:	---
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2026-09-27 01:13:26 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:	2537810

Description Ben Beasley 2026-09-24 21:40:50 UTC

Please branch and build python-wsproto in epel9.

I believe I am already able to do this via python-packagers-sig group co-maintainership, so the purpose of this bug is to ask your consent. The contents of the Rawhide branch build just fine in EPEL9, and you are already maintaining the package in EPEL10. Still, if you don’t want to take care of an additional EPEL branch, you are welcome to add me as an individual co-maintainer (FAS: music).

(Once python-wsproto is in EPEL9, I’ve proven locally that I can branch python-simple-websocket 1.0.0 as comaintainer, then update python-engineio as far as 4.12.3 with some build-system workarounds, and then backport the fixes for CVE-2026-48802 and CVE-2026-48809.)

Comment 1 Carl George 🤠 2026-09-25 01:51:12 UTC

> I believe I am already able to do this via python-packagers-sig group co-maintainership, so the purpose of this bug is to ask your consent.

That's correct, commit permission via group is sufficient to request branches.  I trust you a lot so I wouldn't have batted an eye at you requesting the branch without asking, but nothing wrong with being sure.  Thanks for the consideration!

> The contents of the Rawhide branch build just fine in EPEL9, and you are already maintaining the package in EPEL10. Still, if you don’t want to take care of an additional EPEL branch, you are welcome to add me as an individual co-maintainer (FAS: music).

This reminds me that I need to update rawhide from 1.2.0 to 1.3.2, but that won't be usable for epel9 because 1.2.0 is the last version that has Python 3.9 compatibility, so I'll do it later.  I'll start the epel9 branch on the same commit as epel10, everything newer than that right now is just rebuild commits.

I'll also note that this means that we won't ever be able to update epel9 past 1.2.0, so if there are any future security issues they'll have to be fixed with backports, not rebases.  That's not a blocker, and hopefully will not ever matter, but I just wanted to comment on it as a note to my future self.

I've requested the branch and created the initial build.

Comment 2 Fedora Update System 2026-09-25 01:51:21 UTC

FEDORA-EPEL-2026-cffbee97d3 (python-wsproto-1.2.0-9.el9) has been submitted as an update to Fedora EPEL 9.
https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2026-cffbee97d3

Comment 3 Ben Beasley 2026-09-25 06:21:10 UTC

Thank you!

Comment 4 Fedora Update System 2026-09-26 02:01:08 UTC

FEDORA-EPEL-2026-cffbee97d3 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-2026-cffbee97d3

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

Comment 5 Fedora Update System 2026-09-27 01:13:26 UTC

FEDORA-EPEL-2026-cffbee97d3 (python-wsproto-1.2.0-9.el9) has been pushed to the Fedora EPEL 9 stable repository.
If problem still persists, please make note of it in this bug report.