Comments
carlwgeorge
provided feedback
on golang-github-evanw-esbuild-0.27.2-2.el9
4 months ago
The automated tests tab is showing mixed results.
fedora-ci.koji-build.installability.functional fails, but on a closer look this is because the downgrade portion fails. This is expected since the current version in the repos fails to install. The rest of the check passes.
fedora-ci.koji-build.rmdepcheck.functional correctly reports success. I also double verified with a manual install from the koji build.
carlwgeorge
commented & provided feedback
on python-azure-keyvault-secrets-4.7.0-13.el10_3, …
4 months ago
This fixes the upgrade path problem in #2482445. Thanks for the quick turnaround!
Still affected by the same missing dependency as FEDORA-EPEL-2026-dd471b32c7.
cutter-re-2.1.0-1.el8 from this update is missing dependencies that prevent it from being installed. I've removed it from the repos until this can get sorted out. See #2457202 for more details.
cutter-re-2.2.0-1.el8 from this update is missing dependencies that prevent it from being installed. I've removed it from the repos until this can get sorted out. See #2457202 for more details.
cutter-re-2.3.4-6.el8 from this update is missing dependencies that prevent it from being installed. I've removed it from the repos until this can get sorted out. See #2457202 for more details.
cutter-re-2.3.4-6.el9 from this update is missing dependencies that prevent it from being installed. I've removed it from the repos until this can get sorted out. See #2457203 for more details.
rmdepcheck is reporting a problem (see the automated tests tab above):
New dependency problems in the tested packages themselves:
package: nix-devel-2.31.5-1.el10_2.x86_64
pkgconfig(dep139660765297648)
pkgconfig(dep139660765406336)
pkgconfig(dep139660765484848)
pkgconfig(dep139660767947488)
pkgconfig(dep139660770715136)
pkgconfig(dep139660770902336)
pkgconfig(dep139660771404512)
pkgconfig(dep139660771528864)
pkgconfig(dep139660774698704)
pkgconfig(dep139660776672720)
ERROR:run_rmdepcheck.py:Rmdepcheck failed!
Also confirmed in a container by attempting to install nix-devel:
Error:
Problem: cannot install the best candidate for the job
- nothing provides pkgconfig(dep139660765297648) needed by nix-devel-2.31.5-1.el10_2.x86_64 from epel-testing
- nothing provides pkgconfig(dep139660765406336) needed by nix-devel-2.31.5-1.el10_2.x86_64 from epel-testing
- nothing provides pkgconfig(dep139660765484848) needed by nix-devel-2.31.5-1.el10_2.x86_64 from epel-testing
- nothing provides pkgconfig(dep139660767947488) needed by nix-devel-2.31.5-1.el10_2.x86_64 from epel-testing
- nothing provides pkgconfig(dep139660770715136) needed by nix-devel-2.31.5-1.el10_2.x86_64 from epel-testing
- nothing provides pkgconfig(dep139660770902336) needed by nix-devel-2.31.5-1.el10_2.x86_64 from epel-testing
- nothing provides pkgconfig(dep139660771404512) needed by nix-devel-2.31.5-1.el10_2.x86_64 from epel-testing
- nothing provides pkgconfig(dep139660771528864) needed by nix-devel-2.31.5-1.el10_2.x86_64 from epel-testing
- nothing provides pkgconfig(dep139660774698704) needed by nix-devel-2.31.5-1.el10_2.x86_64 from epel-testing
- nothing provides pkgconfig(dep139660776672720) needed by nix-devel-2.31.5-1.el10_2.x86_64 from epel-testing
FYI, this dependency problem was also caught by rmdepcheck, which you can observe on the automated tests tab above.
Error:
Problem 1: cannot install the best candidate for the job
- nothing provides mpich(x86-64) = 1:4.1.1 needed by petsc-mpich-1:3.20.6-2.el9.x86_64 from epel-testing
Problem 2: cannot install the best candidate for the job
- nothing provides mpich-devel(x86-64) = 1:4.1.1 needed by petsc-mpich-devel-1:3.20.6-2.el9.x86_64 from epel-testing
Problem 3: cannot install the best candidate for the job
- nothing provides mpich(x86-64) = 1:4.1.1 needed by python3-petsc-mpich-1:3.20.6-2.el9.x86_64 from epel-testing
Works as intended to set inhibit-logout to false by default.
Error:
Problem: problem with installed package selinux-policy-42.1.17-1.el10.noarch
- package bitcoin-core-server-31.0-2.el10_2.x86_64 from epel-testing requires (bitcoin-core-selinux >= 0.1 if selinux-policy), but none of the providers can be installed
- cannot install the best candidate for the job
Error:
Problem: problem with installed package selinux-policy-42.1.19-1.el10.noarch
- package bitcoin-core-server-31.0-2.el10_3.x86_64 from epel-testing requires (bitcoin-core-selinux >= 0.1 if selinux-policy), but none of the providers can be installed
- cannot install the best candidate for the job
Actually I just manually tagged rbenv-1.3.2-4.el9 for epel9, since it was already signed and has been in testing for plenty of time. That will be fewer steps and probably less problematic than sending a signed build back through the whole pipeline.
This update has been unpushed.
Welp, I guess not.
Cannot submit ruby-build ('0', '20260412', '3.el9') to stable since it is older than ('0', '20260422', '1.el9')
The only thing I can do is unpush this build, and rbenv-1.3.2-4.el9 will need to be submitted separately.
ruby-build-20260422-1.el9 was pushed to stable before this update (ruby-build-20260412-3.el9).
I would just unpush this update, but it also includes rbenv-1.3.2-4.el9. I'm going to push this one to stable so that goes out, and then retag the newer ruby-build so that it is the one that is included in the next compose.
Yup, I saw that PR, that's where commit 2a9685c came from.