Hi, Please branch and build ipython in epel10. Cheers, Romain
It seems this eventually create a circular dependency with python-stack-data. To build python-stack-data, we need python-executing, which needs ipython. Most likely there is some bootstrapping or some doc/test disabling to do.
*** Bug 2336290 has been marked as a duplicate of this bug. ***
If you do not wish to maintain python-sphinx-basic-ng in epel10, or do not think you will be able to do this in a timely manner, I would be happy to be a co-maintainer of the package (FAS: kkeithle); please add me through https://src.fedoraproject.org/rpms/python-ipython/adduser
python-executing can be built without tests, which drops the ipython BuildRequire. rpmbuild -ba --without=tests --without=slow_tests Then you can build python-stack-data and python-jedi which are also needed for ipython. Once those exist, I can branch and build ipython. But to do this I need all of the BuildRequires for ipython in EPEL.
FEDORA-EPEL-2025-a293b023b2 (ipython-8.31.0-2.el10_0) has been submitted as an update to Fedora EPEL 10.0. https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2025-a293b023b2
FEDORA-EPEL-2025-a293b023b2 has been pushed to the Fedora EPEL 10.0 testing repository. You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2025-a293b023b2 See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.
The proposed updated does not install. Please take a look at the missing dependencies.
One option would be to "bootstrap" this without the python3-ipython+notebook subpackage until all the +notebook dependencies are resolved. scratch build https://koji.fedoraproject.org/koji/taskinfo?taskID=129655927
Yes I also think we should do that, I am trying to release the notebook dependencies and quite some do depend on ipython.
(In reply to Romain Geissler from comment #9) > Yes I also think we should do that, I am trying to release the notebook > dependencies and quite some do depend on ipython. Are you saying there's a circular dependency? That would be a good argument *for* a bootstrap build.
At least for some tests yes, but I didn't check if there is also a circular dependency for runtime dependencies. For now I haven't dig enough to really know what depends on what exactly, but I can tell you that in the python-jupyter-* packages that I recently asked in EPEL and which are needed to build python-notebook I saw multiple times dependencies on ipython. My plan was to actually propose a bootstrap of ipython without the notebook sub package, but I was waiting to have more concrete information before proposing this.
> One option would be to "bootstrap" this without the python3-ipython+notebook subpackage until all the +notebook dependencies are resolved. It's totally fine to make the +notebook subpackage conditional and disable it on releases that don't have the necessary dependencies available. Those type of subpackages are inherently optional. I would just caution against making them literal bootstrap builds (`%bcond bootstrap 1` or `%bcond_without bootstrap` in the spec file, or `_with_bootstrap=1` on a sidetag) because that will add `~bootstrap` to the release, which ideally wouldn't be released to the stable repos. > Are you saying there's a circular dependency? That would be a good argument *for* a bootstrap build. I don't think that is the case, I don't see anything in rawhide that requires +notebook. I think Romain is referring to python-jupyter-* packages that require python-ipython itself, not the +notebook subpackage.
FEDORA-EPEL-2025-f440f7f8c0 (ipython-8.31.0-4.el10_1) has been submitted as an update to Fedora EPEL 10.1. https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2025-f440f7f8c0
FEDORA-EPEL-2025-2752762aa1 (ipython-8.32.0-2.el10_1) has been submitted as an update to Fedora EPEL 10.1. https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2025-2752762aa1
> I would just caution against making them literal bootstrap builds (`%bcond bootstrap 1` or `%bcond_without bootstrap` in the spec file, or `_with_bootstrap=1` on a sidetag) because that will add `~bootstrap` to the release, which ideally wouldn't be released to the stable repos. So bootstrap package shall ideally never hit any user installation ? Because we have been doing that on couple of other packages these last months, so I thought it was "ok-ish". > I don't think that is the case, I don't see anything in rawhide that requires +notebook. I think Romain is referring to python-jupyter-* packages that require python-ipython itself, not the +notebook subpackage. Yes this is what I meant. Shall we create a duplicate bug tracker for releasing the "full" ipython thing with all subpackages once the notebook/jupyter dependencies will be out ?
(In reply to Romain Geissler from comment #15) > > Shall we create a duplicate bug tracker for releasing the "full" ipython > thing with all subpackages once the notebook/jupyter dependencies will be > out ? yes ;-)
> So bootstrap package shall ideally never hit any user installation ? Because we have been doing that on couple of other packages these last months, so I thought it was "ok-ish". Correct. It doesn't inherently break anything as the tilde character handles upgrade path sorting, so it's not the end of the world. But people familiar with bootstrap builds will generally look at it as "this package was built in an incomplete way to break a dependency loop", and people not familiar with bootstrap builds will just wonder "why does this build have so many extra characters?" or "what is a bootstrap build anyways?" or similar confusion. If it's a long term change such as disabling tests, docs, or optional subpackages, better to do that with a normal release bump instead. > Shall we create a duplicate bug tracker for releasing the "full" ipython thing with all subpackages once the notebook/jupyter dependencies will be out ? Good idea.
FEDORA-EPEL-2025-2752762aa1 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-2752762aa1 See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.
FEDORA-EPEL-2025-2752762aa1 (ipython-8.32.0-2.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.