When installing packages with yum or rpm at work, I often wrestled with dependency errors. (For example, if you want to install the GNOME desktop on a Linux server.) This time, I would like to output how to deal with dependency errors that are being done in the actual workplace.
The following error will occur.
[root]# rpm -ivh compat-libstdc++-33-3.2.3-69.el6.i686.rpm
warning: compat-libstdc++-33-3.2.3-69.el6.i686.rpm:Header V3 RSA/SHA256 Signature, key ID fd431d51: NOKEY
error:Lack of dependency:
libc.so.6 is compat-libstdc++-33-3.2.3-69.el6.Required for i686
libc.so.6(GLIBC_2.0)Is compat-libstdc++-33-3.2.3-69.el6.Required for i686
libc.so.6(GLIBC_2.1)Is compat-libstdc++-33-3.2.3-69.el6.Required for i686
libc.so.6(GLIBC_2.1.3)Is compat-libstdc++-33-3.2.3-69.el6.Required for i686
libc.so.6(GLIBC_2.2)Is compat-libstdc++-33-3.2.3-69.el6.Required for i686
libc.so.6(GLIBC_2.3)Is compat-libstdc++-33-3.2.3-69.el6.Required for i686
libgcc_s.so.1 is compat-libstdc++-33-3.2.3-69.el6.Required for i686
libgcc_s.so.1(GCC_3.0)Is compat-libstdc++-33-3.2.3-69.el6.Required for i686
libgcc_s.so.1(GCC_3.3)Is compat-libstdc++-33-3.2.3-69.el6.Required for i686
libgcc_s.so.1(GLIBC_2.0)Is compat-libstdc++-33-3.2.3-69.el6.Required for i686
libm.so.6 is compat-libstdc++-33-3.2.3-69.el6.Required for i686
item | Contents |
---|---|
OS | RHEL/CentOS |
Repository destination | In-house local repository/ISO file |
This is the first troubleshooting method you have come up with in the field.
For example, suppose you get a dependency error when installing a package.
①RHEL7.3(Your existing machine)To RHEL7.Install GNOME desktop with yum using ISO 3
(2) A dependency error is displayed and installation is not possible.
Here's what we were actually doing when dealing with such dependency errors.
① Minor version sets the upper ISO(Example:RHEL7.6 mag)
② Repository setting/Clear cache/Repository read
③ Install GNOME desktop again with yum
Even if you execute "1. Mount the local repository / ISO file whose minor version is one level higher", it is a solution when the dependency error is displayed.
As a countermeasure, it will be like this.
① Set so that you can access multiple repository destinations(Repository settings, etc.)
② Install again with yum
Uninstall the package detected by the dependency error.
yum remove <Cause package>
** This is not recommended for your existing server. ** **
This is because it can affect the service.
It is safer to find a way other than removing the package.
** * If you use this method, be sure to investigate whether the package can be deleted! ** **
** What to do if a dependency error occurs **