Thursday, April 5, 2018

linux - can not install glibc-devel 'Requires: libnss_files.so.2' error

I'm using Linux 6.1
I need to install glibc-devel but it fails with this error.



[root@server1 Packages]# yum install glibc-devel-2.12-1.25.el6.i686.rpm
Loaded plugins: refresh-packagekit
Setting up Install Process

Examining glibc-devel-2.12-1.25.el6.i686.rpm: glibc-devel-2.12-1.25.el6.i686
Marking glibc-devel-2.12-1.25.el6.i686.rpm to be installed
Resolving Dependencies
--> Running transaction check
---> Package glibc-devel.i686 0:2.12-1.25.el6 will be installed
--> Processing Dependency: libBrokenLocale.so.1 for package: glibc-devel-2.12-1.25.el6.i686
--> Processing Dependency: libanl.so.1 for package: glibc-devel-2.12-1.25.el6.i686
--> Processing Dependency: libcidn.so.1 for package: glibc-devel-2.12-1.25.el6.i686
--> Processing Dependency: libcrypt.so.1 for package: glibc-devel-2.12-1.25.el6.i686
--> Processing Dependency: libdl.so.2 for package: glibc-devel-2.12-1.25.el6.i686

--> Processing Dependency: libm.so.6 for package: glibc-devel-2.12-1.25.el6.i686
--> Processing Dependency: libnsl.so.1 for package: glibc-devel-2.12-1.25.el6.i686
--> Processing Dependency: libnss_compat.so.2 for package: glibc-devel-2.12-1.25.el6.i686
--> Processing Dependency: libnss_dns.so.2 for package: glibc-devel-2.12-1.25.el6.i686
--> Processing Dependency: libnss_files.so.2 for package: glibc-devel-2.12-1.25.el6.i686
--> Processing Dependency: libnss_hesiod.so.2 for package: glibc-devel-2.12-1.25.el6.i686
--> Processing Dependency: libnss_nis.so.2 for package: glibc-devel-2.12-1.25.el6.i686
--> Processing Dependency: libnss_nisplus.so.2 for package: glibc-devel-2.12-1.25.el6.i686
--> Processing Dependency: libresolv.so.2 for package: glibc-devel-2.12-1.25.el6.i686
--> Processing Dependency: librt.so.1 for package: glibc-devel-2.12-1.25.el6.i686

--> Processing Dependency: libthread_db.so.1 for package: glibc-devel-2.12-1.25.el6.i686
--> Processing Dependency: libutil.so.1 for package: glibc-devel-2.12-1.25.el6.i686
--> Finished Dependency Resolution
Error: Package: glibc-devel-2.12-1.25.el6.i686 (/glibc-devel-2.12-1.25.el6.i686)
Requires: libnss_files.so.2
Error: Package: glibc-devel-2.12-1.25.el6.i686 (/glibc-devel-2.12-1.25.el6.i686)
Requires: libutil.so.1
Error: Package: glibc-devel-2.12-1.25.el6.i686 (/glibc-devel-2.12-1.25.el6.i686)
Requires: libnss_dns.so.2
Error: Package: glibc-devel-2.12-1.25.el6.i686 (/glibc-devel-2.12-1.25.el6.i686)

Requires: libnss_compat.so.2
Error: Package: glibc-devel-2.12-1.25.el6.i686 (/glibc-devel-2.12-1.25.el6.i686)
Requires: libanl.so.1
Error: Package: glibc-devel-2.12-1.25.el6.i686 (/glibc-devel-2.12-1.25.el6.i686)
Requires: librt.so.1
Error: Package: glibc-devel-2.12-1.25.el6.i686 (/glibc-devel-2.12-1.25.el6.i686)
Requires: libthread_db.so.1
Error: Package: glibc-devel-2.12-1.25.el6.i686 (/glibc-devel-2.12-1.25.el6.i686)
Requires: libm.so.6
Error: Package: glibc-devel-2.12-1.25.el6.i686 (/glibc-devel-2.12-1.25.el6.i686)

Requires: libnss_nis.so.2
Error: Package: glibc-devel-2.12-1.25.el6.i686 (/glibc-devel-2.12-1.25.el6.i686)
Requires: libnsl.so.1
Error: Package: glibc-devel-2.12-1.25.el6.i686 (/glibc-devel-2.12-1.25.el6.i686)
Requires: libnss_nisplus.so.2
Error: Package: glibc-devel-2.12-1.25.el6.i686 (/glibc-devel-2.12-1.25.el6.i686)
Requires: libnss_hesiod.so.2
Error: Package: glibc-devel-2.12-1.25.el6.i686 (/glibc-devel-2.12-1.25.el6.i686)
Requires: libcrypt.so.1
Error: Package: glibc-devel-2.12-1.25.el6.i686 (/glibc-devel-2.12-1.25.el6.i686)

Requires: libresolv.so.2
Error: Package: glibc-devel-2.12-1.25.el6.i686 (/glibc-devel-2.12-1.25.el6.i686)
Requires: libdl.so.2
Error: Package: glibc-devel-2.12-1.25.el6.i686 (/glibc-devel-2.12-1.25.el6.i686)
Requires: libcidn.so.1
Error: Package: glibc-devel-2.12-1.25.el6.i686 (/glibc-devel-2.12-1.25.el6.i686)
Requires: libBrokenLocale.so.1
You could try using --skip-broken to work around the problem
You could try running: rpm -Va --nofiles --nodigest

No comments:

Post a Comment

linux - How to SSH to ec2 instance in VPC private subnet via NAT server

I have created a VPC in aws with a public subnet and a private subnet. The private subnet does not have direct access to external network. S...