Centos 6.7 Yum没有做错。

时间:2020-12-09 22:52:00

My dedicated server is running on Centos 6.7 Yum does not seem to be working at all. Whichever package I try to install with Yum, does not work at all following No package "xyx" available and nothing to do error.

我的专用服务器运行在Centos 6.7 Yum似乎根本不工作。无论我尝试用Yum安装哪个包,都不会在没有包“xyx”的情况下工作,也不会出错。

How do reset the whole yum to default.

如何重置整个yum的默认。

I tried with

我试着用

yum update

and

yum clean all

nothing works.

没有什么工作。

Example: when I try to install a package.

当我尝试安装一个包时。

root@ns321982 [~]# sudo yum install -y tigervnc-server
Setting up Install Process
No package tigervnc-server available.
Error: Nothing to do
root@ns321982 [~]# subscription-manager list
-bash: subscription-manager: command not found
root@ns321982 [~]# yum search tigervnc-server
No Matches found

Example: When I try to update yum

当我试图更新yum的时候。

root@ns321982 [~]# yum update
Setting up Update Process
base                                                                       | 3.4 kB     00:00
base/primary_db                                                            | 4.3 MB     00:00
epel/metalink                                                              |  25 kB     00:00
epel                                                                       | 4.3 kB     00:00
epel/primary_db                                                            | 5.0 MB     00:00
extras                                                                     | 3.4 kB     00:00
extras/primary_db                                                          |  30 kB     00:00
updates                                                                    | 3.4 kB     00:00
updates/primary_db                                                         | 4.3 MB     00:00
Resolving Dependencies
--> Running transaction check
---> Package bind.i686 32:9.8.2-0.30.rc1.el6_6.1 will be updated
--> Processing Dependency: bind = 32:9.8.2-0.30.rc1.el6_6.1 for package: 32:bind-chroot-9.8.2-0.30.rc1.el6_6.1.i686
---> Package bind.i686 32:9.8.2-0.37.rc1.el6_7.7 will be an update
---> Package bind-devel.i686 32:9.8.2-0.30.rc1.el6_6.1 will be updated
---> Package bind-devel.i686 32:9.8.2-0.37.rc1.el6_7.7 will be an update
---> Package bind-libs.i686 32:9.8.2-0.30.rc1.el6_6.1 will be updated
---> Package bind-libs.i686 32:9.8.2-0.37.rc1.el6_7.7 will be an update
---> Package bind-utils.i686 32:9.8.2-0.30.rc1.el6_6.1 will be updated
---> Package bind-utils.i686 32:9.8.2-0.37.rc1.el6_7.7 will be an update
---> Package initscripts.i686 0:9.03.46-1.el6.centos.1 will be updated
---> Package initscripts.i686 0:9.03.49-1.el6.centos.4 will be an update
--> Processing Dependency: sysvinit-tools >= 2.87-6 for package: initscripts-9.03.49-1.el6.centos.4.i686
--> Processing Dependency: module-init-tools >= 3.9-25 for package: initscripts-9.03.49-1.el6.centos.4.i686
---> Package libcgroup.i686 0:0.40.rc1-15.el6_6 will be updated
---> Package libcgroup.i686 0:0.40.rc1-17.el6_7 will be an update
---> Package ntpdate.i686 0:4.2.6p5-2.el6.centos will be updated
---> Package ntpdate.i686 0:4.2.6p5-5.el6.centos.4 will be an update
---> Package openssh.i686 0:5.3p1-104.el6_6.1 will be updated
---> Package openssh.i686 0:5.3p1-114.el6_7 will be an update
---> Package openssh-clients.i686 0:5.3p1-104.el6_6.1 will be updated
---> Package openssh-clients.i686 0:5.3p1-114.el6_7 will be an update
---> Package openssh-server.i686 0:5.3p1-104.el6_6.1 will be updated
---> Package openssh-server.i686 0:5.3p1-114.el6_7 will be an update
--> Finished Dependency Resolution
Error: Package: 32:bind-chroot-9.8.2-0.30.rc1.el6_6.1.i686 (@updates)
           Requires: bind = 32:9.8.2-0.30.rc1.el6_6.1
           Removing: 32:bind-9.8.2-0.30.rc1.el6_6.1.i686 (@updates)
               bind = 32:9.8.2-0.30.rc1.el6_6.1
           Updated By: 32:bind-9.8.2-0.37.rc1.el6_7.7.i686 (base)
               bind = 32:9.8.2-0.37.rc1.el6_7.7
           Available: 32:bind-9.8.2-0.37.rc1.el6_7.1.i686 (base)
               bind = 32:9.8.2-0.37.rc1.el6_7.1
           Available: 32:bind-9.8.2-0.37.rc1.el6_7.2.i686 (base)
               bind = 32:9.8.2-0.37.rc1.el6_7.2
           Available: 32:bind-9.8.2-0.37.rc1.el6_7.4.i686 (base)
               bind = 32:9.8.2-0.37.rc1.el6_7.4
           Available: 32:bind-9.8.2-0.37.rc1.el6_7.5.i686 (base)
               bind = 32:9.8.2-0.37.rc1.el6_7.5
           Available: 32:bind-9.8.2-0.37.rc1.el6_7.6.i686 (base)
               bind = 32:9.8.2-0.37.rc1.el6_7.6
Error: Package: initscripts-9.03.49-1.el6.centos.4.i686 (base)
           Requires: module-init-tools >= 3.9-25
           Installed: module-init-tools-3.9-24.el6.i686 (@base)
               module-init-tools = 3.9-24.el6
Error: Package: initscripts-9.03.49-1.el6.centos.4.i686 (base)
           Requires: sysvinit-tools >= 2.87-6
           Installed: sysvinit-tools-2.87-5.dsf.el6.i686 (@base)
               sysvinit-tools = 2.87-5.dsf.el6
 You could try using --skip-broken to work around the problem
 You could try running: rpm -Va --nofiles --nodigest

Return when I type

返回当我类型

root@ns321982 [~]# yum repolist
repo id                   repo name                                                      status
base                      CentOS-6 - Base                                                1,068+103
epel                      Extra Packages for Enterprise Linux 6 - i386                   9,199+710
extras                    CentOS-6 - Extras                                                     40
updates                   CentOS-6 - Updates                                             1,068+103
repolist: 11,375

I basically want to install desktop environment like GNOME so that I can control dedicated hosting server remotely using GUI.

我基本上想要安装桌面环境,比如GNOME,这样我就可以使用GUI远程控制专用的主机服务器。

1 个解决方案

#1


0  

There are same packages with different versions on different repositories. Run yum info bind-chroot to find out which repositories provide bind-chroot package (You should do that for initscripts package.

在不同的存储库中有不同版本的相同包。运行yum info bind-chroot来查找哪些存储库提供了绑定包(您应该为initscripts包这样做)。

After finding repositories that provide same packages, keep the most update/stable one and disable the other/others.

在找到提供相同包的存储库之后,保持最更新/稳定的包并禁用其他/其他。

I think extras repository may cause the problem. You can disable it and retry to run yum update

我认为额外的存储库可能会导致问题。您可以禁用它并重试运行yum更新。

#1


0  

There are same packages with different versions on different repositories. Run yum info bind-chroot to find out which repositories provide bind-chroot package (You should do that for initscripts package.

在不同的存储库中有不同版本的相同包。运行yum info bind-chroot来查找哪些存储库提供了绑定包(您应该为initscripts包这样做)。

After finding repositories that provide same packages, keep the most update/stable one and disable the other/others.

在找到提供相同包的存储库之后,保持最更新/稳定的包并禁用其他/其他。

I think extras repository may cause the problem. You can disable it and retry to run yum update

我认为额外的存储库可能会导致问题。您可以禁用它并重试运行yum更新。