Bug 2348949

Summary:	Please branch and build python-jupyter-server-terminals in epel10
Product:	[Fedora] Fedora	Reporter:	Romain Geissler <romain.geissler>
Component:	python-jupyter-server-terminals	Assignee:	Romain Geissler <romain.geissler>
Status:	CLOSED ERRATA	QA Contact:
Severity:	medium	Docs Contact:
Priority:	unspecified
Version:	rawhide	CC:	lbalhar
Target Milestone:	---
Target Release:	---
Hardware:	Unspecified
OS:	Linux
Whiteboard:
Fixed In Version:	python-jupyter-server-terminals-0.5.3-5.el10_1	Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2025-03-10 01:03:08 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:	2348950
Bug Blocks:	2347203

Description Romain Geissler 2025-02-27 23:43:35 UTC

Hi,

Please branch and build python-jupyter-server-terminals in epel10.

I may help co-maintaining the EPEL branches (fas id: romaingeissler1a)

Reproducible: Always

Comment 1 Lumír Balhar 2025-02-28 09:47:50 UTC

I've added you as a collaborator for epel* branches.

Comment 2 Fedora Update System 2025-03-01 09:07:31 UTC

FEDORA-EPEL-2025-490ca27bdb (python-jupyter-server-terminals-0.5.3-5.el10_1) has been submitted as an update to Fedora EPEL 10.1.
https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2025-490ca27bdb

Comment 3 Fedora Update System 2025-03-02 01:22:11 UTC

FEDORA-EPEL-2025-490ca27bdb 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-490ca27bdb

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

Comment 4 Fedora Update System 2025-03-10 01:03:08 UTC

FEDORA-EPEL-2025-490ca27bdb (python-jupyter-server-terminals-0.5.3-5.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.