You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Error:
Problem 1: cannot install the best candidate for the job
- nothing provides /usr/bin/escript needed by cactuscore-uhal-tests-2.8.9-1.el9.gcc11_3_1.x86_64
Problem 2: cannot install the best candidate for the job
- nothing provides /usr/bin/escript needed by cactuscore-controlhub-2.8.9-1.el9.x86_64
Problem 3: package cactuscore-uhal-python39-2.8.9-1.el9.gcc11_3_1.x86_64 requires libcactus_uhal_tests.so.2.8()(64bit), but none of the providers can be installed
- cannot install the best candidate for the job
- nothing provides /usr/bin/escript needed by cactuscore-uhal-tests-2.8.5-1.el9.gcc11_3_1.x86_64
- nothing provides /usr/bin/escript needed by cactuscore-uhal-tests-2.8.6-1.el9.gcc11_3_1.x86_64
- nothing provides /usr/bin/escript needed by cactuscore-uhal-tests-2.8.7-1.el9.gcc11_3_1.x86_64
- nothing provides /usr/bin/escript needed by cactuscore-uhal-tests-2.8.8-1.el9.gcc11_3_1.x86_64
- nothing provides /usr/bin/escript needed by cactuscore-uhal-tests-2.8.9-1.el9.gcc11_3_1.x86_64
(try to add '--skip-broken' to skip uninstallable packages or '--nobest' to use not only best candidate packages)
The text was updated successfully, but these errors were encountered:
Unfortunately EPEL9 doesn't yet contain Erlang packages, which is the source of this problem. The workaround that I've used on Alma9 so far is to install Erlang from the Fedora 34 repos instead, which can be added with the following commands:
We are using IPBus to control the prototype hardware for the DUNE timing system and the systems at CERN are being moved to Alma 9. We want to know if it is OK to update to Alma 9 or we will have to work around issues if we do.
The only issue that I've had to work around is the lack of Erlang RPMs in Alma 9 (this only affects the ControlHub, not uHAL - in case the ControlHub is running on different machines than the uHAL-based SW in your setup). However, with the above workaround of installing the Erlang RPMs from the Fedora 34 repos instead, the ControlHub works fine in our CI tests.
Here is the error message after the command:
sudo yum groupinstall uhal controlhub
The text was updated successfully, but these errors were encountered: