马上注册,结交更多好友,享用更多功能,让你轻松玩转社区。
您需要 登录 才可以下载或查看,没有账号?注册
×
![}X8YM3I~3VFNO[1KU`RRJGC.png X8YM3I~3VFNO1KU `RRJGC.png](https://forum-gitlab-cn-1308186353.cos.ap-shanghai.myqcloud.com/bbs/forum/202406/05/101552ids768hqxhqxhrsq.png)
sudo EXTERNAL_URL="https://gitlab.example.com" yum install -y gitlab-jh
Loaded plugins: fastestmirror, langpacks
Loading mirror speeds from cached hostfile
epel/x86_64/metalink | 6.4 kB 00:00
One of the configured repositories failed (gitlab_gitlab-ce-source),
and yum doesn't have enough cached data to continue. At this point the only
safe thing yum can do is fail. There are a few ways to work "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=gitlab_gitlab-ce-source ...
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 gitlab_gitlab-ce-source
or
subscription-manager repos --disable=gitlab_gitlab-ce-source
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=gitlab_gitlab-ce-source.skip_if_unavailable=true
failure: repodata/repomd.xml from gitlab_gitlab-ce-source: [Errno 256] No more mirrors to try.
https://packages.gitlab.com/gitlab/gitlab-ce/el/7/SRPMS/repodata/repomd.xml: [Errno 14] HTTPS Error 302 - Found |