Comments
carlwgeorge
The automated test failure seems to be having a problem rendering. I manually verified this package installs.
With FEDORA-EPEL-2025-65e100abca it looks like this is now installable.
This resolves the nexus installation issue.
Of course, happy to help.
Just so you're aware we did get installability checks enabled for the leading EPEL 10 minor version. If you look at the "Automated Tests" tab above there is a red indicator next to it, and if you switch to the tab it shows what the failure is. It isn't perfect, but it's a start to help catch things like this before they move to stable.
This does not install.
Error:
Problem: conflicting requests
- nothing provides torsocks needed by tor-0.4.8.14-1.el10_1.x86_64 from epel-testing
This does not install.
Error:
Problem 1: conflicting requests
- nothing provides (python3.12dist(pyqt5-sip) < 13~~ with python3.12dist(pyqt5-sip) >= 12.13) needed by python3-qt5-base-5.15.10-11.el10_0.x86_64 from @commandline
Problem 2: package python3-qt5-5.15.10-11.el10_0.x86_64 from @commandline requires python3-qt5-base(x86-64) = 5.15.10-11.el10_0, but none of the providers can be installed
- conflicting requests
- nothing provides (python3.12dist(pyqt5-sip) < 13~~ with python3.12dist(pyqt5-sip) >= 12.13) needed by python3-qt5-base-5.15.10-11.el10_0.x86_64 from @commandline
This does not install.
Error:
Problem: package python3-qt5-5.15.10-11.el10_1.x86_64 from epel-testing requires python3-qt5-base(x86-64) = 5.15.10-11.el10_1, but none of the providers can be installed
- conflicting requests
- nothing provides (python3.12dist(pyqt5-sip) < 13~~ with python3.12dist(pyqt5-sip) >= 12.13) needed by python3-qt5-base-5.15.10-11.el10_1.x86_64 from epel-testing
The dask subpackage does not install.
Error:
Problem: conflicting requests
- nothing provides python3.12dist(dask) needed by python3-fsspec+dask-2024.12.0-3.el10_1~bootstrap.noarch from epel-testing
- nothing provides python3.12dist(distributed) needed by python3-fsspec+dask-2024.12.0-3.el10_1~bootstrap.noarch from epel-testing
This is also a bootstrap build that probably not should be published. If the tests need to be disabled for an extended period of time while dependencies are worked on, please do that as a normal release bump and conditionals.
This does not install.
Error:
Problem: conflicting requests
- nothing provides webkit2gtk3 needed by minigalaxy-1.3.2-1.el10_1.noarch from epel-testing
Doesn't install.
Error:
Problem: conflicting requests
- nothing provides linuxconsoletools needed by gpm-1.20.7-48.el10_0.x86_64 from @commandline
The request bug for this already depends on the linuxconsoletools request bug.
Doesn't install.
Error:
Problem: conflicting requests
- nothing provides linuxconsoletools needed by gpm-1.20.7-48.el10_1.x86_64 from @commandline
The request bug for this already depends on the linuxconsoletools request bug.
Now that this is moving to stable, I have tagged these builds for 10.1 too as described in this post. They will be included in the next 10.0 and 10.1 composes.
The automated test failure is due to the downgrade section, which is expected because the current package in the repos fails to install. This new update installs fine.
I think all the missing dependencies have been taken care of now, so you can push this to stable when you're ready. Because we're after the point of the epel10.0 mass branching, this will only go to the EPEL 10.0 repo, not the new EPEL 10.1 repo. I can manually tag these builds forward to add them once they move to stable.
Please note that the automated installability check is enabled for EPEL 10 now. This was flagged as not installable and should not have been pushed. This has been addressed by adding cpuinfo in the following updates.
I created the missing update as a proven packager to resolve the installation issue for svt-av1-libs.
Thanks!
This update has been unpushed.
Ah, it's the python3-uvicorn+standard subpackage, which will fail to install until python-httptools-0.6.4-2.el10_1 and python-uvloop-0.21.0-1.el10_1 move to stable. Autopush is already disabled on this update to ensure it doesn't get promoted to stable before those updates.