Yum Update encountered dependency error resolution in Linux

Redhat series of Linux system Yum, sometimes the wrong dependencies, with Linux early, encounter this kind of problem is simply helpless, but under the yum of "instigation" under the use of "--skip-broken" parameters, sometimes really can solve the problem, but sometimes the consequences, Can play the system bad, the next boot can not start, or there are other inexplicable problems.

A typical error-dependent message is listed as follows:

--> is processing dependency/usr/sbin/ldconfig, which is libva1-1.3.1-11.el7.x86_64 by the package
--> is processing dependency/usr/sbin/ldconfig, which is libmad0-0.15.1b-4.el7.x86_64 by the package
--> is processing dependency/usr/sbin/ldconfig, which is librtmp0-2.3-1.el7.x86_64 by the package
--> is processing dependency/usr/sbin/ldconfig, which is libx264_142-0.142-20_20140406.2245.el7.x86_64 by the package
--> is processing dependency/usr/sbin/ldconfig, which is libxvidcore4-1.3.2-15.el7.x86_64 by the package
.......
Error: Package: libmad0-0.15.1b-4.el7.x86_64 (@atrpms)
Required:/usr/sbin/ldconfig
Deleting: glibc-2.17-55.el7_0.1.i686 (@updates)
Not found
Update, by: glibc-2.17-55.el7_0.3.i686 (Updates)
Not found
Error: Package: librtmp0-2.3-1.el7.x86_64 (@atrpms)
Required:/usr/sbin/ldconfig
Deleting: glibc-2.17-55.el7_0.1.i686 (@updates)
Not found
Update, by: glibc-2.17-55.el7_0.3.i686 (Updates)
Not found
You can try to add the--skip-broken option to resolve the problem
You can try to execute: Rpm-va--nofiles--nodigest
See the last two lines, usually don't listen to it, be careful!

In order to gracefully handle the problem of a similar error dependency, it is necessary to understand the cause of the problem first. This is usually caused by manually installing some unofficial RPM packages or by using multiple yum sources. In particular, the upgrade installs a new version of the package. For example, in CentOS, in order to install some software, use the package in Fedora to upgrade the system's own package.

Personal experience is as follows:

First remove the/etc/yum.repo.d/from the official source, back to the other directory, deal with the problem and then move back to use.

Yum list to see what source of the package, in addition to @base @anaconda @updates, should pay attention to, according to the "reliable" degree from low to high gradually removed. The "degree of success" here depends on some experience. As listed earlier in this article, the error-dependent example, I used a lot of source packages, @epel @atrpms @nux-dextop @google-chrome, such as several third-party sources, Epel is very high quality, google-chrome only Chrome browser, The other few are not very reliable, first remove them.

Check the package names listed in the Yum list, use Fedora, or non-native schema-like packages (686 of the x64 system), Yum erase remove them. When uninstalling the package, be careful not to uninstall the important System package. Don't do this. With the-y parameter according to the Yum Erase {package name}-y,yum Erase Uninstall a package, the system prompts you to remove which packages, and if it looks wrong, press N

Finally, you will find the problem of the package name, that is, error-dependent information
--> is processing dependency/usr/sbin/ldconfig, which is libbluray1-0.4.0-6.el7.x86_64 by the package
--> Resolve Dependencies Complete
Error: Package: libbluray1-0.4.0-6.el7.x86_64 (@atrpms)
Required:/usr/sbin/ldconfig
Deleting: glibc-2.17-55.el7_0.1.x86_64 (@updates)
Not found
Update, by: glibc-2.17-55.el7_0.3.x86_64 (Updates)
Not found
You can try to add the--skip-broken option to resolve the problem
You can try to execute: Rpm-va--nofiles--nodigest
Will resemble the one shown above, just a few one or two packages, try uninstalling it to see

[ROOT@FSC ~]# rpm-e libbluray1-0.4.0-6.el7.x86_64
Error: Dependency detection failed:

    libbluray.so.1 () (64bit) gvfs-1.16.4-7.el7.x86_64 required
    Libbluray.so.1 () (64bit) gvfs-fuse-1.16.4-7.el7.x86_64 requires
    libbluray.so.1 () (64bit) to be (already Ann) gvfs-afc-1.16.4-7.el7.x86_64 need to
    libbluray.so.1 () (64bit) be (Ann) gvfs-gphoto2-1.16.4-7.el7.x86 _64 need to
    libbluray.so.1 () (64bit) be (already installed) gvfs-goa-1.16.4-7.el7.x86_64 required
    Libbluray.so.1 () (64bit) gvfs-mtp-1.16.4-7.el7.x86_64 requires
    libbluray.so.1 () (64bit) to be (already Ann) gvfs-smb-1.16.4-7.el7.x86_64 need to
    libbluray.so.1 () (64bit) be (Ann) gvfs-afp-1.16.4-7.el7.x86_64 Need
    libbluray.so.1 () (64bit) to be (already installed) gvfs-archive-1.16.4-7.el7.x86_64 required
    Libbluray.so.1 () (64bit) libbluray-0.4.0-6.el7.x86_64 need
    libbluray1 = 0.4.0-6.el7 be (already Ann) L Ibbluray-0.4.0-6.el7.x86_64 requires

Well, check the system for a version of the bag. Rpm-q {Package Name}

In the example above, the package is a ATRPMS source package that is newer than the package in the CentOS source. Recall when in order to install SMPlayer, loaded with a series of ATRPMS package. In the impression, the ATRPMS source sometimes upgrades the CentOS package, so it causes the Yum update to upgrade the system to cause the error dependence. Download this RPM package into the CentOS Mirror, rpm--FORCE-UVH {package file path} cover installation, then try again yum update.

If there's no problem, that's fine. Then move the Yum source configuration file back, yum Makecache, and then install them according to the records of the packages you just unloaded, and refer to the History command records.