I have tried million ways going around this already and nothing seems to help :( Yum-config-manager -save -setopt=.skip_if_unavailable=trueįile /var/cache/yum/armhfp/7/epel/metalink.xml does not exist If it is a very temporary problem though, this is often a nice So will have to try and fail each time (and thus. Note that yum will try to contact the repo. Configure the failing repository to be skipped, if it is unavailable. Will then just ignore the repository until you permanently enable itĪgain or use -enablerepo for temporary usage:ĥ. Disable the repository permanently, so yum won't use it by default. Run the command with the repository temporarily disabledĤ. Packages for the previous distribution release still work).ģ. This is most often useful if you are using a newerĭistribution release than is supported by the repository (and the for the repository, to point to a working Contact the upstream for the repository and get them to fix the problem.Ģ. There are a few ways to work "fix" this:ġ. One of the configured repositories failed (Unknown),Īnd yum doesn't have enough cached data to continue.
#INSTALL HTOP CENTOS 7 INSTALL#
However, now, whenever I try to do something with yum, whether it is update or install of some package it gives me the following error (for example I used yum -y install Python3.6 or I have also tried installing tsclient or python-pip): ]# yum install -y Python3.6 This installs package succesfully and I can see both epel.repo and epel-testing.repo in etc/ (I copy their contains at the end of post) Therefore I tried different approach using RedHat Package Manager:
Sudo yum -y install epel-release (I did of course sudo yum -y update before and it worked fine), but it told me Package 'epel-release' not found So I am trying to install EPEL first by using So I am trying to setup up a ssh bastion server, but I have problem setting up EPEL in order to install Python3.6.
0 kommentar(er)
