+++ This bug was initially created as a clone of Bug #2347200 +++ Hi, Please branch and build python-ipykernel in epel10. Because of some loop dependencies with python-ipyparallel, this will need a first bootstrap build without the tests. Reproducible: Always --- Additional comment from Romain Geissler on 2025-03-01 09:36:43 UTC --- Please note that I can help co-maintaining the EPEL branches to get this released (fas id: romaingeissler1a). --- Additional comment from Romain Geissler on 2025-03-08 14:03:01 UTC --- This will help the EPEL 10 bootstrapping: https://src.fedoraproject.org/rpms/python-ipykernel/pull-request/29 --- Additional comment from Romain Geissler on 2025-03-16 01:08:20 UTC --- @Paulo: would it be possible to add me as collaborator on the EPEL branches (fas id: romaingeissler1a) ? We will need to build this in a side tag, and I expect to build myself other packages too, like the dependency python-jupyter-client. --- Additional comment from Fedora Update System on 2025-03-30 01:03:17 UTC --- FEDORA-EPEL-2025-d6b6409623 (python-ipykernel-6.29.3-11.el10_1~bootstrap, python-jupyter-client-8.6.1-12.el10_1, and 1 more) has been submitted as an update to Fedora EPEL 10.1. https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2025-d6b6409623
This was just built in side tag "epel10.1-build-side-108972", but not promoted yet.
FEDORA-EPEL-2025-c00ce91ec1 (jupyterlab-4.4.2-1.el10_1, python-ipykernel-6.29.3-11.el10_1, and 15 more) has been submitted as an update to Fedora EPEL 10.1. https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2025-c00ce91ec1
FEDORA-EPEL-2025-c00ce91ec1 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-c00ce91ec1 See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.
FEDORA-EPEL-2025-c00ce91ec1 (jupyterlab-4.4.2-1.el10_1, python-ipykernel-6.29.3-11.el10_1, and 15 more) has been pushed to the Fedora EPEL 10.1 stable repository. If problem still persists, please make note of it in this bug report.