(Linux) Small issue record on CentOS 6.6 using 163 yum Source!

Source: Internet
Author: User
Tags gpg

Hey, today in the use of 163 of the source for updates, the following error message appears!

2]# vim readme.md[[email protected] php-5.6.12]# yum clean  All loaded plugins: fastestmirrorcleaning repos: base elrepo extras updates clean everything cleaning up  list of fastest mirrors[[email protected] php-5.6.12]# yum  Makecache Loaded plugin: fastestmirrordetermining fastest mirrors * elrepo: ftp.ne.jphttp:// mirrors.163.com/centos/6/os/x86_64/repodata/repomd.xml: [errno 14] pycurl                                                                                                                                                                       ERROR 22 -  "The requested url returned error: 404 not  found "Try another mirror. Error:cannot retrieve repository metadata  (repomd.xml)  for repository: base.  Ple                                                                                                                                                                     ase verify its  path and try again[[email protected] php-5.6.12]# ping  mirrors.163.comping mirrors.163.com  (123.58.173.185)  56 (+)  bytes of data.64  bytes from 123.58.173.185: icmp_seq=1 ttl=54 time=49.1 ms64 bytes  from 123.58.173.185: icmp_seq=2 TTL=54 TIME=50.7 MS^C--- mirrors.163.com ping statistics ---2  packets transmitted, 2 received, 0% packet loss, time 1113msrtt  min/avg/max/mdev = 49.178/49.939/50.701/0.793 ms[[email protected] ~]#

How am I supposed to repay you? I wget a repo, the result is a version of 6! 6 version also forget, incredibly give me 404! So no way, manually change it!

 # centos-base.repo## the mirror system uses the connecting ip  address of the client and the# update status of each  Mirror to pick mirrors that are updated to and# geographically  close to the client.  you should use this for centos  updates# unless you are manually picking other mirrors.## if  the mirrorlist= does not work for you, as a fall back  you can try the # remarked out baseurl= line instead.##[ base]name=centos-$releasever  - base - 163.combaseurl=http://mirrors.163.com/centos/6.6/os/ $basearch/#mirrorlist =http://mirrorlist.centos.org/?release= $releasever &arch= $basearch &repo=osgpgcheck =1gpgkey=http://mirror.centos.org/centos/rpm-gpg-key-centos-6#released updates [updates]name=centos-$releasever  -  updates - 163.combaseurl=http://mirrors.163.com/centos/6.6/updates/$basearch/#mirrorlist =http:// mirrorlist.centos.org/?release= $releasever &arch= $basearch &repo=updatesgpgcheck=1gpgkey=http:// mirror.centos.org/centos/rpm-gpg-key-centos-6#additional packages that may be useful[ extras]name=centos-$releasever  - extras - 163.combaseurl=http://mirrors.163.com/centos/6.6 /extras/$basearch/#mirrorlist =http://mirrorlist.centos.org/?release= $releasever &arch= $basearch &repo= Extrasgpgcheck=1gpgkey=http://mirror.centos.org/centos/rpm-gpg-key-centos-6#additional packages that  extend functionality of existing packages[centosplus]name=centos-$releasever  -  plus - 163.combaseurl=http://mirrors.163.com/centos/6.6/centosplus/$basearch/#mirrorlist =http ://mirrorlist.centos.org/?release= $releasever &arch= $basearch &repo=centosplusgpgcheck=1enabled=0gpgkey=http://mirror.centos.org/ centos/rpm-gpg-key-centos-6#contrib - packages by centos users[contrib]name=centos-$ releasever - contrib - 163.combaseurl=http://mirrors.163.com/centos/6.6/contrib/$basearch/ #mirrorlist =http://mirrorlist.centos.org/?release= $releasever &arch= $basearch &repo=contribgpgcheck= 1enabled=0gpgkey=http://mirror.centos.org/centos/rpm-gpg-key-centos-6

From then on, the world was quiet again ~~~! 163, how do I love you?

(Linux) Small issue record on CentOS 6.6 using 163 yum Source!

Related Article

Contact Us

The content source of this page is from Internet, which doesn't represent Alibaba Cloud's opinion; products and services mentioned on that page don't have any relationship with Alibaba Cloud. If the content of the page makes you feel confusing, please write us an email, we will handle the problem within 5 days after receiving your email.

If you find any instances of plagiarism from the community, please send an email to: info-contact@alibabacloud.com and provide relevant evidence. A staff member will contact you within 5 working days.

A Free Trial That Lets You Build Big!

Start building with 50+ products and up to 12 months usage for Elastic Compute Service

  • Sales Support

    1 on 1 presale consultation

  • After-Sales Support

    24/7 Technical Support 6 Free Tickets per Quarter Faster Response

  • Alibaba Cloud offers highly flexible support services tailored to meet your exact needs.