The Esaote installation dependency report error message is as follows
One of the configured repositories failed (unknown).
and yum doesn’t have enough cached data to continue. At this point, the only thing yum can do is
The safe thing to do is to fail. There are ways to “fix” this..:

 1. Contact the upstream for the repository and get them to fix the problem.

 2. Reconfigure the baseurl/etc. for the repository, to point to a working
    upstream. This is most often useful if you are using a newer
    distribution release than is supported by the repository (and the
    packages for the previous distribution release still work).

 3. Run the command with the repository temporarily disabled
        yum --disablerepo=<repoid> ...

 4. Disable the repository permanently, so yum won't use it by default. Yum
    will then just ignore the repository until you permanently enable it
    again or use --enablerepo for temporary usage:

        yum-config-manager --disable <repoid>
    or
        subscription-manager repos --disable=<repoid>

 5. Configure the failing repository to be skipped, if it is unavailable.
    Note that yum will try to contact the repo. when it runs most commands,
    so will have to try and fail each time (and thus. yum will be be much
    slower). If it is a very temporary problem though, this is often a nice
    compromise:

        yum-config-manager --save --setopt=<repoid>.skip_if_unavailable=true

Solution
can start by configuring yum sources

1. is generally a network problem, check whether the network is unobvious. Secondly, if you use the company’s internal network, there will be restrictions, it is recommended to change the agent (there may be several agents in the company, but one happens to be limited, so you need to change the agent), you can ask colleagues to. Proxy parameter name error: yum’s proxy should use

proxy

1. , instead of

http_proxy</code b> or https_proxy, but it is recommended to write all three, which must be correct.

For example: yum install-y XXX –proxy IP –http_proxy IP –https_proxy

Read More:

• Fedora32 start container error – OCI runtime create failed: This version of runc doesn’t work on cgroups V2: unknown
• [Solved] selenium.common.exceptions.WebDriverException: Message: unknown error: DevToolsActivePort file doesn
• Solve selenium error — unknown error: devtoolsactivport file doesn’t exist
• Solution to Linux error loading mirror speeds from cached hostfile
• Gradle:Using flatDir should be avoided because it doesn‘t support any meta-data formats.
• Vs_ Code remote SFTP connects to the server to modify the nginx configuration information and reports all configured authentication methods failed
• The Tomcat connector configured to listen on port 7014 failed to start
• PHP error Warning: Unknown: failed to open stream: Permission denied in Unknown on line 0 Fatal error:
• The Tomcat connector configured to listen on port 8080 failed to start. The port may already be in u
• failed call to cuInit: CUDA_ERROR_UNKNOWN: unknown error
• Error in machine learning training data (FIT): valuee rror:Unknown label type:‘continuous‘
• Failed to load response data:No data found for resource with given identifie
• Use yum to prompt Error: rpmdb open failed
• Error in data training: valueerror: unknown label type: ‘continuous‘
• One or more filters failed to start
• Git failed to submit data error: failed to push some refs to’https://github.com/XXXXXXX/gif.git’
• As Error:Failed to find configured root that contains /storage/emulated/0/xxx/xxx/xxx.png
• Add a warehouse in allprojects repositories and report an error
• PSQLException: ERROR: cached plan must not change result type
• CentOS uses Yum install to report errors