Comments
carlwgeorge
This doesn't seem to fix the problem.
Error:
Problem: cannot install the best candidate for the job
- nothing provides python3-django needed by python3-django-tastypie-0.14.7-2.el9.noarch from epel-testing
This build was built against 1b0493a, but the requires fix is in commit 2a9685c. When built from that commit I think it will result in a release of 3 instead of 2.
I've got the fix handled already. The problem is this is a major version update, which is not allowed by the EPEL update policy. The reason we have the policy is to avoid breakages like this.
https://docs.fedoraproject.org/en-US/epel/epel-policy-updates/
In the future, please do not submit major version updates to EPEL branches. If it's truly unavoidable, it must follow the incompat update process to raise awareness and help coordinate necessary related changes.
https://docs.fedoraproject.org/en-US/epel/epel-policy-incompatible-upgrades/
This update broke the installation of python3-httpx+cli.
Error:
Problem: conflicting requests
- nothing provides (python3.12dist(rich) < 14~~ with python3.12dist(rich) >= 10) needed by python3-httpx+cli-0.28.1-2.el10_1.noarch from epel
This update broke the installation of python3-httpx+cli.
Error:
Problem: conflicting requests
- nothing provides (python3.12dist(rich) < 14~~ with python3.12dist(rich) >= 10) needed by python3-httpx+cli-0.28.1-2.el10_1.noarch from epel
This update broke the installation of rust-quanta+prost-types-devel.
Error:
Problem: conflicting requests
- nothing provides (crate(prost-types) >= 0.13.0 with crate(prost-types) < 0.14.0~) needed by rust-quanta+prost-types-devel-0.12.6-2.el10_2.noarch from epel
This update has been unpushed.
Error:
Problem: conflicting requests
- nothing provides fedrq needed by sandogasa-0.10.0-2.el10_2.x86_64 from epel-testing
This update has been unpushed.
Error:
Problem: conflicting requests
- nothing provides fedrq needed by sandogasa-0.10.0-2.el10_3.x86_64 from epel-testing
I just submitted rpms/buildbot#21 to add an import check to help catch issues like this. When building that PR's spec file for epel10, it confirms the same missing dependencies.
No matching package to install: 'python3dist(docker)'
No matching package to install: 'python3dist(klein)'
No matching package to install: 'python3dist(python-novaclient)'
Testing in a container, this resolves the libQt6Qml dependency issue and is installable.
Based on rmdepcheck, there seems to be some missing runtime deps.
package: buildbot-master-container-4.3.0-7.el10_3.noarch from file:///var/ARTIFACTS/work-plank33_j5zj/rmdepcheck/plan/data/repo
python3.12dist(docker)
package: buildbot-master-openstack-4.3.0-7.el10_3.noarch from file:///var/ARTIFACTS/work-plank33_j5zj/rmdepcheck/plan/data/repo
python3.12dist(python-novaclient)
package: buildbot-www-4.3.0-7.el10_3.noarch from file:///var/ARTIFACTS/work-plank33_j5zj/rmdepcheck/plan/data/repo
python3.12dist(klein)
Error:
Problem: conflicting requests
- nothing provides (crate(comfy-table) >= 7.0.0 with crate(comfy-table) < 8.0.0~) needed by rust-arrow-cast+comfy-table-devel-57.3.0-2.el10_3.noarch from epel-testing
This update bumped the library soname from libradcli.so.6 to libradcli.so.10. This is not allowed under the EPEL updates policy.
https://docs.fedoraproject.org/en-US/epel/epel-policy-updates/
Please do not do further soname bumps in the future without following the EPEL incompatible upgrade process.
https://docs.fedoraproject.org/en-US/epel/epel-policy-incompatible-upgrades/
Looks like this is was already broken in the stable repos, see #2459252.
Error:
Problem: conflicting requests
- nothing provides python3-radicale3 = 3.6.1-1.1.el8 needed by radicale3-InfCloud-3.6.1-1.1.el8.noarch from epel
The new 20260412-2.el9 build is now installable, but I noticed that the conditional used causes the requirement to be zlib-devel on Fedora too. This can be observed on the latest rawhide build.
https://koji.fedoraproject.org/koji/rpminfo?rpmID=46870035
I sent an adjustment as a pull request.
https://src.fedoraproject.org/rpms/ruby-build/pull-request/35
Pushing this to stable will break the installation of ocaml-cpdf. That should probably be updated at the same time, in the same update.
Pushing this to stable will break the installation of ocaml-cpdf. That should probably be updated at the same time, in the same update.
Yup, I saw that PR, that's where commit 2a9685c came from.