Comments
carlwgeorge
If you've got a dependency loop or otherwise closely related packages, please build them in a side tag so the builds involved can be released together. Builds that do not install should not be released.
This update has been unpushed.
The python3-numcodecs+zfpy subpackage in this update is not installable. This was detected by the automated installability test (see the "Automated Tests" tab above). Unfortunately, that is currently non-blocking. Please take note of that tab in the future to avoid letting uninstallable updates be promoted to stable.
This package is not installable, which was detected by the automated installability test (see the "Automated Tests" tab above). Unfortunately, that is currently non-blocking. Please take note of that tab in the future to avoid letting uninstallable updates be promoted to stable.
Slight correction, the dnsperf-queryparse subpackage is not installable (dnsperf installs fine).
This package is not installable, which was detected by the automated installability test (see the "Automated Tests" tab above). Unfortunately, that is currently non-blocking. Please take note of that tab in the future to avoid letting uninstallable updates be promoted to stable.
This package is not installable, which was detected by the automated installability test (see the "Automated Tests" tab above). Unfortunately, that is currently non-blocking. Please take note of that tab in the future to avoid letting uninstallable updates be promoted to stable.
This update has been unpushed.
As shown in the automated installability test, rocm-rpm-macros-modules from this update doesn't install.
Error:
Problem: conflicting requests
- nothing provides rocm-llvm-filesystem needed by rocm-rpm-macros-modules-6.4.0-4.el10_1.noarch from brew-133806555
python3-tensile-devel from this update doesn't install.
Error:
Problem: conflicting requests
- nothing provides hipcc needed by python3-tensile-devel-6.4.0-1.el10_1.noarch from brew-133808338
- nothing provides rocminfo needed by python3-tensile-devel-6.4.0-1.el10_1.noarch from brew-133808338
Just a workflow note, if this had been submitted in the same update as nagios-4.5.9-1.el10_1 and nagios-plugins-2.4.12-1.el10_1, the dependencies would have resolved for the installability test and it would be showing a green check instead of a red minus on the automated tests tab above. This is also important to ensure the builds move to stable at the same time.
Just a workflow note, if this had been submitted in the same update as nagios-plugins-2.4.12-1.el10_1, the dependencies would have resolved for the installability test and it would be showing a green check instead of a red minus on the automated tests tab above. This is also important to ensure the builds move to stable at the same time.
Just a workflow note, if this had been submitted in the same update as nagios-4.5.9-1.el10_1, the dependencies would have resolved for the installability test and it would be showing a green check instead of a red minus on the automated tests tab above.
This build was untagged, see #2365774 for more details.
I can confirm this resolves #2367431, thanks!
This is not installable.
Error:
Problem: package R-4.5.0-3.el10_1.x86_64 from epel requires R-devel(x86-64) = 4.5.0-3.el10_1, but none of the providers can be installed
- conflicting requests
- nothing provides R-rpm-macros needed by R-devel-4.5.0-3.el10_1.x86_64 from epel
Files as https://bugzilla.redhat.com/show_bug.cgi?id=2367431
This seems to be missing a dependency.
Error:
Problem: conflicting requests
- nothing provides telepathy-mission-control needed by spacebar-1:6.3.5-1.el10_0.x86_64 from epel-testing
This seems to be missing a dependency.
Error:
Problem: conflicting requests
- nothing provides telepathy-mission-control needed by spacebar-1:6.3.5-1.el10_1.x86_64 from epel-testing
This update has
rocm-compilersupport-19-11.rocm6.4.1.el10_1~bootstrap. Generally, bootstrap builds are used only for bootstrapping, and aren't released. I see in that spec file the bootstrapping is related to rocm-runtime-devel, which is part of this update. The way this would normally work is:For this workflow to work the spec file needs to always have bootstrap disabled (not gated on the fedora/rhel macros), and rely on bootstrap being enabled outside of the spec file. Would you mind doing a new non-bootstrap build of rocm-compilersupport in this side tag?
Also, unrelated to the bootstrap thing, can you tag python-tensile-6.4.0-1.el10_1 into the side tag so it's included in this update and is released at the same time as it's dependencies?