I want to install an rpm from a repo just once and not have to add it to my yum.repos.d/ directory using the tmprepo plugin. However, I’m blocked on how to install an rpm with no gpg signature. The ‘—nogpgcheck’ option doesn’t work with the tmprepo plugin and I need to manually append ‘pkgs_gpgcheck=false’ to /etc/yum/pluginconf.d/tmprepo.conf. sudo yum --tmprepo=http://edge.artifactory.example.com:8000/artifactory/chef_rpms/rhel/chef_rpms.repo --nogpgcheck install chef ## ^^ this fails as —nogpgcheck doesn’t work with tmprepo which defaults to gpgcheck unless I manually edit /etc/yum/pluginconf.d/tmprepo.conf Any way this can be done when calling yum on command line? I don’t want to go about changing a file on the system for a one-time thing. Thanks! - Faheem

I would like to subscribe to the following Oracle yum repository so I can install virtual box guest additions packages. Where can I find the .repo file URL in order for me to add this to my Oracle Linux subscription list? Edit: I am already subscribed to the Oracle public yum repo [root@localhost yum.repos.d]# yum repolist Loaded plugins: langpacks, ulninfo repo id repo name status ol6_UEK_latest/x86_64 Latest Unbreakable Enterprise Kernel for Oracle Lin 820 ol6_latest/x86_64 Oracle Linux 7Server Latest (x86_64) 11,323 ol7_UEKR5/x86_64 Latest Unbreakable Enterprise Kernel Release 5 for 108 ol7_latest/x86_64 Oracle Linux 7Server Latest (x86_64) 11,688 repolist: 23,939 [root@localhost yum.repos.d]# yum search vbox Loaded plugins: langpacks, ulninfo ============================== N/S matched: vbox =============================== isdn4k-utils-vboxgetty.x86_64 : ISDN voice box (getty) Name and summary matches only, use "search all" for everything.

Is there a real way to install gcc without yum on CentOS 7? On my system yum doesn't work: yum update -bash: /usr/bin/yum: /usr/bin/python2.7: bad interpreter: No such file or directory And when I want to install python2.7 it needs GCC that I don't know where it is on my system? which gcc /usr/bin/which: no gcc in (/root/anaconda2/bin:/root/anaconda3/bin:/root/anaconda3/condabin:/usr/local/bin:/usr/local/bin:/usr/local/bin:/root/anaconda3/bin:/root/anaconda3/condabin:/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/root/bin:/root/bin) And when I search how to install GCC without yum, most of them need yum! Is there really a way to solve this problem?

While following https://access.redhat.com/solutions/64069 General documentation of the system state both prior to and after patching is always good practice. This should include running package-cleanup with following flags, --orphans, --problems, --dupes, --leaves. Looking for orphans (packages which are not available from currently configured repositories) I did get kernel-3.10.0-1127.el7.x86_64 and it would be true, because I've installed CentOS 7.8 and upgraded to 7.9 and the kernel package is in the https://vault.centos.org/7.8.2003/os/Source/SPackages/ repo not the 7.9. [root@localhost boot]# package-cleanup --orphans Loaded plugins: fastestmirror Loading mirror speeds from cached hostfile * base: centos.wielun.net * extras: centos.wielun.net * updates: centos.wielun.net kernel-3.10.0-1127.el7.x86_64 [root@localhost boot]# rpm -qa kernel kernel-3.10.0-1160.6.1.el7.x86_64 kernel-3.10.0-1127.el7.x86_64 I can imagine that it would be advisable to run the above command in case I would like to use yum history undo to revert last made changes, and that a given rpm package would have to be available on the system, but if it was not removed during yum update then do I need really to care if the package is marked as orphaned ? Next, I executed the following command, to get a list of leaves ( Leaf nodes are RPMs that are not relied upon by any other RPM): [root@localhost boot]# package-cleanup --leaves Loaded plugins: fastestmirror libsysfs-2.1.0-16.el7.x86_64 [root@localhost boot]# rpm -q --requires libsysfs-2.1.0-16.el7.x86_64 /sbin/ldconfig /sbin/ldconfig libc.so.6()(64bit) libc.so.6(GLIBC_2.2.5)(64bit) libc.so.6(GLIBC_2.3.4)(64bit) libc.so.6(GLIBC_2.4)(64bit) rpmlib(CompressedFileNames) Running transaction check ---> Package libsysfs.x86_64 0:2.1.0-16.el7 will be erased --> Finished Dependency Resolution Dependencies Resolved ============================================================================================================================================================================================= Package Arch Version Repository Size ============================================================================================================================================================================================= Removing: libsysfs x86_64 2.1.0-16.el7 @anaconda 146 k Transaction Summary ============================================================================================================================================================================================= Remove 1 Package Per my understanding yum resolved all the dependencies and it looks like I'm free to remove the pacakage, but I'm wondering about the output of the rpm -q --provides command. Is it correct to say that the 3 items listed is stuff that got installed together with the libsysfs.x86_64 0:2.1.0-16.el7 package AND since yum resolved all dependencies and no other stuff on the system requires this package + the packages/shared libraries it provides it can be removed without any issues ? If that is true, why I'm not able to list the files installed as part of that rpm ? [root@localhost boot]# rpm -qa libsysfs libsysfs-2.1.0-16.el7.x86_64 [root@localhost boot]# [root@localhost boot]# [root@localhost boot]# rpm -qlp libsysfs-2.1.0-16.el7.x86_64 error: open of libsysfs-2.1.0-16.el7.x86_64 failed: No such file or directory Thank you for any clarification is possible !

> **What specific syntax needs to be changed or added to the below in order for commands calling python in a RHEL7 VM to be interpreted using Python3 WITHOUT breaking programs like yum that require Python2?** **FIRST ATTEMPT:** Our first attempt was to add the following 2 lines to the very end of the cloud-init startup script which instantiates the VM: rm /usr/bin/python ln -s /usr/bin/python3 /usr/bin/python **ERROR THAT RESULTED:** The problem is that adding the above two lines to the end of the cloud-init startup script causes yum commands to break when yum is called afterwards as follows: $ sudo yum update -y File "/bin/yum", line 30 except KeyboardInterrupt, e: ^ SyntaxError: invalid syntax $ **TOGGLING THE ERROR:** We can turn off the error by removing the above 2 lines from the cloud-init startup script and re-instantiating a new replacement VM. This isolates the source of the problem, but still we have the problem of how to default python to Python3 without breaking apps like yum.

I need to install few RPM files within a TeradataToolsAndUtilitiesBase__linux_x8664.17.00.31.00.tar.gz from URL below and the file name is "TTU 17.10.11.00 Linux - Base" https://downloads.teradata.com/download/tools/teradata-tools-and-utilities-linux-installation-package-0 how can we do install by using command line by using either yum or rpm.

I'm running Oracle Linux/RHEL and trying to get a list of installed packages whose name/arch is not in any active repository. When doing yum list installed these packages are displayed in red, but is there any yum command to only list those?

I am trying to install the epel-release package from the CentOS extras repository, but the repository seems to be empty. (I'm also pretty new to linux) When I run yum repolist: Loaded plugins: fastestmirror, langpacks Loading mirror speeds from cached hostfile repo id repo name status base/7/i386 CentOS-7 - Base 7,114 extras/7/i386 CentOS-7 - Extras 0 updates/7/i386 CentOS-7 - Updates 1,437 repolist: 8,551 When I run yum list extras: Loaded plugins: fastestmirror, langpacks Loading mirror speeds from cached hostfile I have tried running yum clean all and yum update, but nothing has seemed to work. Output of hostnamectl: Static hostname: localhost.localdomain Icon name: computer-vm Chassis: vm Machine ID: 4925cfdbb53e4e18b5ce1e3bd2d4ce0d Boot ID: b3109364c8a14af9b37a81599f900755 Virtualization: oracle Operating System: CentOS 7 (AltArch) CPE OS Name: cpe:/o:centos:centos:7 Kernel: Linux 3.10.0-514.16.1.el7.centos.plus.i686 Architecture: x86 Output of rpm --query centos-release: centos-release-7-3.1611.el7.centos.i686

I'm truing to run yum update, and keep getting errors about conflicts. I must have accidentally interrupted an update at some point, but I don't know when and how. I've tried —skip-broken, but it doesn't really help me, because I want to update the parts that now refuse to update. Also, I've tried "yum remove util-linux", but then when I tried to re-install it, it didn't let me. Due to conflict errors much like what I'm getting now. (So I reverted to a backup volume, hence back on square 1). Any ideas of how I can solve this? yum update Loaded plugins: priorities, update-motd, upgrade-helper amzn-main/latest | 2.1 kB 00:00 amzn-updates/latest | 2.3 kB 00:00 Resolving Dependencies --> Running transaction check ---> Package aws-amitools-ec2.noarch 0:1.5.2-0.0.amzn1 will be updated ---> Package aws-amitools-ec2.noarch 0:1.5.3-0.0.amzn1 will be an update ---> Package aws-apitools-as.noarch 0:1.0.61.4-1.0.amzn1 will be updated ---> Package aws-apitools-as.noarch 0:1.0.61.5-1.0.amzn1 will be an update ---> Package aws-apitools-ec2.noarch 0:1.6.13.0-1.1.amzn1 will be updated ---> Package aws-apitools-ec2.noarch 0:1.7.1.0-1.2.amzn1 will be an update ---> Package aws-apitools-elb.noarch 0:1.0.34.0-1.0.amzn1 will be updated ---> Package aws-apitools-elb.noarch 0:1.0.35.0-1.0.amzn1 will be an update ---> Package aws-cli.noarch 0:1.3.6-1.0.amzn1 will be updated ---> Package aws-cli.noarch 0:1.3.24-1.0.amzn1 will be an update ---> Package cloud-init.noarch 0:0.5.15-77.amzn1 will be updated ---> Package cloud-init.noarch 0:0.7.2-7.20.amzn1 will be updated ---> Package cloud-init.noarch 0:0.7.2-7.27.amzn1 will be an update ---> Package curl.x86_64 0:7.35.0-2.42.amzn1 will be updated ---> Package curl.x86_64 0:7.36.0-2.44.amzn1 will be updated ---> Package curl.x86_64 0:7.36.0-2.45.amzn1 will be an update ---> Package cyrus-sasl.x86_64 0:2.1.23-13.13.amzn1 will be updated ---> Package cyrus-sasl.x86_64 0:2.1.23-13.15.amzn1 will be an update ---> Package cyrus-sasl-lib.x86_64 0:2.1.23-13.10.amzn1 will be updated ---> Package cyrus-sasl-lib.x86_64 0:2.1.23-13.13.amzn1 will be updated ---> Package cyrus-sasl-lib.x86_64 0:2.1.23-13.15.amzn1 will be an update ---> Package cyrus-sasl-plain.x86_64 0:2.1.23-13.10.amzn1 will be updated ---> Package cyrus-sasl-plain.x86_64 0:2.1.23-13.13.amzn1 will be updated ---> Package cyrus-sasl-plain.x86_64 0:2.1.23-13.15.amzn1 will be an update ---> Package ec2-net-utils.noarch 0:0.4-1.20.amzn1 will be updated ---> Package ec2-net-utils.noarch 0:0.4-1.22.amzn1 will be an update ---> Package ec2-utils.noarch 0:0.4-1.20.amzn1 will be updated ---> Package ec2-utils.noarch 0:0.4-1.22.amzn1 will be an update ---> Package elfutils-libelf.x86_64 0:0.152-1.12.amzn1 will be updated ---> Package elfutils-libelf.x86_64 0:0.157-2.14.amzn1 will be updated ---> Package elfutils-libelf.x86_64 0:0.158-3.16.amzn1 will be an update ---> Package file.x86_64 0:5.11-13.14.amzn1 will be updated ---> Package file.x86_64 0:5.11-13.16.amzn1 will be updated ---> Package file.x86_64 0:5.19-1.18.amzn1 will be an update ---> Package file-libs.x86_64 0:5.11-13.14.amzn1 will be updated ---> Package file-libs.x86_64 0:5.11-13.16.amzn1 will be updated ---> Package file-libs.x86_64 0:5.19-1.18.amzn1 will be an update ---> Package glibc.x86_64 0:2.12-1.132.45.amzn1 will be updated ---> Package glibc.x86_64 0:2.17-36.81.amzn1 will be updated ---> Package glibc.x86_64 0:2.17-55.84.amzn1 will be an update ---> Package glibc-common.x86_64 0:2.12-1.132.45.amzn1 will be updated ---> Package glibc-common.x86_64 0:2.17-36.81.amzn1 will be updated ---> Package glibc-common.x86_64 0:2.17-55.84.amzn1 will be an update ---> Package glibc-devel.x86_64 0:2.17-36.81.amzn1 will be updated ---> Package glibc-devel.x86_64 0:2.17-55.84.amzn1 will be an update ---> Package glibc-headers.x86_64 0:2.17-36.81.amzn1 will be updated ---> Package glibc-headers.x86_64 0:2.17-55.84.amzn1 will be an update ---> Package gnupg2.x86_64 0:2.0.22-1.24.amzn1 will be updated ---> Package gnupg2.x86_64 0:2.0.24-1.25.amzn1 will be an update ---> Package httpd.x86_64 0:2.2.27-1.2.amzn1 will be updated ---> Package httpd.x86_64 0:2.2.27-1.3.amzn1 will be an update ---> Package httpd-tools.x86_64 0:2.2.27-1.2.amzn1 will be updated ---> Package httpd-tools.x86_64 0:2.2.27-1.3.amzn1 will be an update ---> Package java-1.6.0-openjdk.x86_64 1:1.6.0.0-66.1.13.1.62.amzn1 will be updated ---> Package java-1.6.0-openjdk.x86_64 1:1.6.0.0-66.1.13.1.63.amzn1 will be updated ---> Package java-1.6.0-openjdk.x86_64 1:1.6.0.0-67.1.13.4.65.amzn1 will be an update ---> Package kernel.x86_64 0:3.10.48-55.140.amzn1 will be installed ---> Package kernel-headers.x86_64 0:3.10.35-43.137.amzn1 will be updated ---> Package kernel-headers.x86_64 0:3.10.48-55.140.amzn1 will be an update ---> Package libblkid.x86_64 0:2.17.2-13.17.amzn1 will be updated ---> Package libblkid.x86_64 0:2.23.2-6.21.amzn1 will be updated ---> Package libblkid.x86_64 0:2.23.2-16.22.amzn1 will be an update ---> Package libcurl.x86_64 0:7.35.0-2.42.amzn1 will be updated ---> Package libcurl.x86_64 0:7.36.0-2.44.amzn1 will be updated ---> Package libcurl.x86_64 0:7.36.0-2.45.amzn1 will be an update ---> Package libmount.x86_64 0:2.23.2-6.21.amzn1 will be updated ---> Package libmount.x86_64 0:2.23.2-16.22.amzn1 will be an update ---> Package libpwquality.x86_64 0:1.2.3-1.2.amzn1 will be updated ---> Package libpwquality.x86_64 0:1.2.3-1.5.amzn1 will be an update ---> Package libtasn1.x86_64 0:2.3-3.4.amzn1 will be updated ---> Package libtasn1.x86_64 0:2.3-6.6.amzn1 will be an update ---> Package libuuid.x86_64 0:2.17.2-13.17.amzn1 will be updated ---> Package libuuid.x86_64 0:2.23.2-6.21.amzn1 will be updated ---> Package libuuid.x86_64 0:2.23.2-16.22.amzn1 will be an update ---> Package libxml2.x86_64 0:2.9.1-1.1.28.amzn1 will be updated ---> Package libxml2.x86_64 0:2.9.1-1.1.29.amzn1 will be updated ---> Package libxml2.x86_64 0:2.9.1-1.1.31.amzn1 will be an update ---> Package mod_ssl.x86_64 1:2.2.27-1.2.amzn1 will be updated ---> Package mod_ssl.x86_64 1:2.2.27-1.3.amzn1 will be an update ---> Package mysql55.x86_64 0:5.5.34-1.40.amzn1 will be updated ---> Package mysql55.x86_64 0:5.5.36-1.44.amzn1 will be updated ---> Package mysql55.x86_64 0:5.5.38-1.0.amzn1 will be an update ---> Package mysql55-common.x86_64 0:5.5.34-1.40.amzn1 will be updated ---> Package mysql55-common.x86_64 0:5.5.36-1.44.amzn1 will be updated ---> Package mysql55-common.x86_64 0:5.5.38-1.0.amzn1 will be an update ---> Package mysql55-libs.x86_64 0:5.5.34-1.40.amzn1 will be updated ---> Package mysql55-libs.x86_64 0:5.5.36-1.44.amzn1 will be updated ---> Package mysql55-libs.x86_64 0:5.5.38-1.0.amzn1 will be an update ---> Package mysql55-server.x86_64 0:5.5.34-1.40.amzn1 will be updated ---> Package mysql55-server.x86_64 0:5.5.36-1.44.amzn1 will be updated ---> Package mysql55-server.x86_64 0:5.5.38-1.0.amzn1 will be an update ---> Package nspr.x86_64 0:4.10.2-1.19.amzn1 will be updated ---> Package nspr.x86_64 0:4.10.4-1.22.amzn1 will be an update ---> Package nss.x86_64 0:3.15.3-3.32.amzn1 will be updated ---> Package nss.x86_64 0:3.16.0-1.36.amzn1 will be an update ---> Package nss-softokn.x86_64 0:3.14.3-9.15.amzn1 will be updated ---> Package nss-softokn.x86_64 0:3.16.0-1.19.amzn1 will be an update ---> Package nss-softokn-freebl.x86_64 0:3.14.3-9.15.amzn1 will be updated ---> Package nss-softokn-freebl.x86_64 0:3.16.0-1.19.amzn1 will be an update ---> Package nss-sysinit.x86_64 0:3.15.3-3.32.amzn1 will be updated ---> Package nss-sysinit.x86_64 0:3.16.0-1.36.amzn1 will be an update ---> Package nss-tools.x86_64 0:3.15.3-3.32.amzn1 will be updated ---> Package nss-tools.x86_64 0:3.16.0-1.36.amzn1 will be an update ---> Package nss-util.x86_64 0:3.15.3-1.18.amzn1 will be updated ---> Package nss-util.x86_64 0:3.15.3-1.19.amzn1 will be updated ---> Package nss-util.x86_64 0:3.16.0-1.22.amzn1 will be an update ---> Package openssh.x86_64 0:6.2p2-7.40.amzn1 will be updated ---> Package openssh.x86_64 0:6.2p2-8.41.amzn1 will be an update ---> Package openssh-clients.x86_64 0:6.2p2-7.40.amzn1 will be updated ---> Package openssh-clients.x86_64 0:6.2p2-8.41.amzn1 will be an update ---> Package openssh-server.x86_64 0:6.2p2-7.40.amzn1 will be updated ---> Package openssh-server.x86_64 0:6.2p2-8.41.amzn1 will be an update ---> Package openssl.x86_64 1:1.0.1e-4.55.amzn1 will be updated ---> Package openssl.x86_64 1:1.0.1g-1.69.amzn1 will be updated ---> Package openssl.x86_64 1:1.0.1i-1.78.amzn1 will be an update ---> Package pam.x86_64 0:1.1.1-13.20.amzn1 will be updated ---> Package pam.x86_64 0:1.1.8-1.25.amzn1 will be updated ---> Package pam.x86_64 0:1.1.8-9.29.amzn1 will be an update ---> Package python-boto.noarch 0:2.27.0-1.0.amzn1 will be updated ---> Package python-boto.noarch 0:2.32.0-1.0.amzn1 will be an update ---> Package python-botocore.noarch 0:0.40.0-1.0.amzn1 will be updated ---> Package python-botocore.noarch 0:0.58.0-1.0.amzn1 will be an update ---> Package python-jmespath.noarch 0:0.3.1-1.0.amzn1 will be updated ---> Package python-jmespath.noarch 0:0.4.1-1.0.amzn1 will be an update ---> Package python-simplejson.x86_64 0:3.3.0-1.5.amzn1 will be updated ---> Package python-simplejson.x86_64 0:3.5.3-1.7.amzn1 will be an update ---> Package readline.x86_64 0:6.0-4.12.amzn1 will be updated ---> Package readline.x86_64 0:6.2-6.13.amzn1 will be updated ---> Package readline.x86_64 0:6.2-9.14.amzn1 will be an update ---> Package util-linux.x86_64 0:2.23.2-6.21.amzn1 will be updated ---> Package util-linux.x86_64 0:2.23.2-16.22.amzn1 will be obsoleting ---> Package util-linux-ng.x86_64 0:2.17.2-13.17.amzn1 will be obsoleted --> Processing Conflict: glibc-2.17-55.84.amzn1.x86_64 conflicts audit Processing Conflict: util-linux-2.23.2-16.22.amzn1.x86_64 conflicts coreutils Processing Conflict: util-linux-2.23.2-16.22.amzn1.x86_64 conflicts sysvinit Processing Conflict: util-linux-2.23.2-16.22.amzn1.x86_64 conflicts sysvinit Finished Dependency Resolution --> Running transaction check ---> Package glibc.x86_64 0:2.17-36.81.amzn1 will be updated ---> Package glibc.x86_64 0:2.17-36.81.amzn1 will be updated ---> Package kernel.x86_64 0:3.4.76-65.111.amzn1 will be erased --> Processing Conflict: glibc-2.17-55.84.amzn1.x86_64 conflicts audit Processing Conflict: util-linux-2.23.2-16.22.amzn1.x86_64 conflicts coreutils Processing Conflict: util-linux-2.23.2-16.22.amzn1.x86_64 conflicts sysvinit Processing Conflict: util-linux-2.23.2-16.22.amzn1.x86_64 conflicts sysvinit Finished Dependency Resolution Error: util-linux conflicts with coreutils-8.4-31.20.amzn1.x86_64 Error: util-linux conflicts with sysvinit-2.87-4.dsf.10.amzn1.x86_64 Error: util-linux conflicts with upstart-0.6.5-12.10.amzn1.x86_64 Error: glibc conflicts with audit-2.2-2.17.amzn1.x86_64 You could try using --skip-broken to work around the problem ** Found 113 pre-existing rpmdb problem(s), 'yum check' output follows: apr-1.5.0-2.11.amzn1.x86_64 is a duplicate with apr-1.4.6-1.10.amzn1.x86_64 audit-2.3.2-3.19.amzn1.x86_64 is a duplicate with audit-2.2-2.17.amzn1.x86_64 audit-libs-2.3.2-3.19.amzn1.x86_64 is a duplicate with audit-libs-2.2-2.17.amzn1.x86_64 ca-certificates-2013.1.94-65.0.9.amzn1.noarch is a duplicate with ca-certificates-2012.1.95-3.12.amzn1.noarch cloud-init-0.7.2-7.20.amzn1.noarch is a duplicate with cloud-init-0.5.15-77.amzn1.noarch coreutils-8.21-13.31.amzn1.x86_64 is a duplicate with coreutils-8.4-31.20.amzn1.x86_64 cronie-anacron-1.4.4-7.5.amzn1.x86_64 has missing requires of cronie = ('0', '1.4.4', '7.5.amzn1') cronie-anacron-1.4.4-12.6.amzn1.x86_64 is a duplicate with cronie-anacron-1.4.4-7.5.amzn1.x86_64 cryptsetup-1.6.2-2.11.amzn1.x86_64 is a duplicate with cryptsetup-1.5.1-1.3.amzn1.x86_64 cryptsetup-libs-1.6.2-2.11.amzn1.x86_64 is a duplicate with cryptsetup-libs-1.5.1-1.3.amzn1.x86_64 curl-7.36.0-2.44.amzn1.x86_64 is a duplicate with curl-7.35.0-2.42.amzn1.x86_64 cyrus-sasl-lib-2.1.23-13.13.amzn1.x86_64 is a duplicate with cyrus-sasl-lib-2.1.23-13.10.amzn1.x86_64 cyrus-sasl-plain-2.1.23-13.13.amzn1.x86_64 is a duplicate with cyrus-sasl-plain-2.1.23-13.10.amzn1.x86_64 db4-4.7.25-18.11.amzn1.x86_64 is a duplicate with db4-4.7.25-17.10.amzn1.x86_64 db4-utils-4.7.25-18.11.amzn1.x86_64 is a duplicate with db4-utils-4.7.25-17.10.amzn1.x86_64 1:dbus-1.6.12-5.25.amzn1.x86_64 is a duplicate with 1:dbus-1.2.24-7.16.amzn1.x86_64 1:dbus-libs-1.6.12-5.25.amzn1.x86_64 is a duplicate with 1:dbus-libs-1.2.24-7.16.amzn1.x86_64 dejavu-fonts-common-2.33-5.8.amzn1.noarch is a duplicate with dejavu-fonts-common-2.30-2.4.amzn1.noarch dejavu-sans-fonts-2.33-5.8.amzn1.noarch is a duplicate with dejavu-sans-fonts-2.30-2.4.amzn1.noarch dejavu-serif-fonts-2.33-5.8.amzn1.noarch is a duplicate with dejavu-serif-fonts-2.30-2.4.amzn1.noarch 12:dhclient-4.1.1-38.P1.19.amzn1.x86_64 is a duplicate with 12:dhclient-4.1.1-34.P1.18.amzn1.x86_64 12:dhcp-common-4.1.1-38.P1.19.amzn1.x86_64 is a duplicate with 12:dhcp-common-4.1.1-34.P1.18.amzn1.x86_64 e2fsprogs-libs-1.42.8-2.29.amzn1.x86_64 is a duplicate with e2fsprogs-libs-1.42.3-3.17.amzn1.x86_64 elfutils-libelf-0.157-2.14.amzn1.x86_64 is a duplicate with elfutils-libelf-0.152-1.12.amzn1.x86_64 file-5.11-13.16.amzn1.x86_64 is a duplicate with file-5.11-13.14.amzn1.x86_64 file-libs-5.11-13.16.amzn1.x86_64 is a duplicate with file-libs-5.11-13.14.amzn1.x86_64 glib2-2.36.3-2.14.amzn1.x86_64 is a duplicate with glib2-2.22.5-7.11.amzn1.x86_64 glibc-2.17-36.81.amzn1.x86_64 has installed conflicts audit < ('0', '2.3.0', None): audit-2.2-2.17.amzn1.x86_64 glibc-2.17-36.81.amzn1.x86_64 is a duplicate with glibc-2.12-1.132.45.amzn1.x86_64 glibc-common-2.17-36.81.amzn1.x86_64 is a duplicate with glibc-common-2.12-1.132.45.amzn1.x86_64 groff-1.22.2-6.10.amzn1.x86_64 is a duplicate with groff-1.18.1.4-21.7.amzn1.x86_64 groff-base-1.22.2-6.10.amzn1.x86_64 has installed conflicts groff < ('0', '1.22.2', None): groff-1.18.1.4-21.7.amzn1.x86_64 grubby-7.0.15-5.7.amzn1.x86_64 is a duplicate with grubby-7.0.15-3.6.amzn1.x86_64 gzip-1.5-4.16.amzn1.x86_64 is a duplicate with gzip-1.3.12-19.9.amzn1.x86_64 hwdata-0.233-9.1.16.amzn1.noarch is a duplicate with hwdata-0.233-7.9.14.amzn1.noarch info-5.1-1.9.amzn1.x86_64 is a duplicate with info-4.13a-8.8.amzn1.x86_64 initscripts-9.03.40-2.29.amzn1.x86_64 has installed conflicts util-linux-ng < ('0', '2.23', None): util-linux-ng-2.17.2-13.17.amzn1.x86_64 initscripts-9.03.40-2.29.amzn1.x86_64 has installed conflicts util-linux < ('0', '2.23', None): util-linux-ng-2.17.2-13.17.amzn1.x86_64 initscripts-9.03.40-2.29.amzn1.x86_64 is a duplicate with initscripts-9.03.38-1.22.amzn1.x86_64 1:java-1.6.0-openjdk-1.6.0.0-66.1.13.1.63.amzn1.x86_64 is a duplicate with 1:java-1.6.0-openjdk-1.6.0.0-66.1.13.1.62.amzn1.x86_64 kpartx-0.4.9-72.7.amzn1.x86_64 is a duplicate with kpartx-0.4.9-64.6.amzn1.x86_64 ksh-20120801-10.12.amzn1.x86_64 is a duplicate with ksh-20100621-19.11.amzn1.x86_64 libblkid-2.23.2-6.21.amzn1.x86_64 is a duplicate with libblkid-2.17.2-13.17.amzn1.x86_64 libcom_err-1.42.8-2.29.amzn1.x86_64 is a duplicate with libcom_err-1.42.3-3.17.amzn1.x86_64 libcurl-7.36.0-2.44.amzn1.x86_64 is a duplicate with libcurl-7.35.0-2.42.amzn1.x86_64 libgcrypt-1.5.3-1.14.amzn1.x86_64 is a duplicate with libgcrypt-1.4.5-9.12.amzn1.x86_64 14:libpcap-1.4.0-1.20130826git2dbcaa1.10.amzn1.x86_64 is a duplicate with 14:libpcap-1.0.0-6.20091201git117cb5.9.amzn1.x86_64 libss-1.42.8-2.29.amzn1.x86_64 is a duplicate with libss-1.42.3-3.17.amzn1.x86_64 libtool-ltdl-2.4.2-18.4.8.2.21.amzn1.x86_64 is a duplicate with libtool-ltdl-2.2.10-4.6.3.14.amzn1.x86_64 libudev-173-4.13.amzn1.x86_64 is a duplicate with libudev-173-4.12.amzn1.x86_64 libuuid-2.23.2-6.21.amzn1.x86_64 is a duplicate with libuuid-2.17.2-13.17.amzn1.x86_64 libxml2-2.9.1-1.1.29.amzn1.x86_64 is a duplicate with libxml2-2.9.1-1.1.28.amzn1.x86_64 libxslt-1.1.28-3.8.amzn1.x86_64 is a duplicate with libxslt-1.1.26-2.7.amzn1.x86_64 libyaml-0.1.6-1.6.amzn1.x86_64 is a duplicate with libyaml-0.1.4-6.5.amzn1.x86_64 mdadm-3.2.6-7.29.amzn1.x86_64 is a duplicate with mdadm-3.2.5-4.23.amzn1.x86_64 mysql-5.5-1.6.amzn1.noarch is a duplicate with mysql-5.5-1.3.amzn1.noarch mysql-server-5.5-1.6.amzn1.noarch is a duplicate with mysql-server-5.5-1.3.amzn1.noarch mysql55-5.5.36-1.44.amzn1.x86_64 is a duplicate with mysql55-5.5.34-1.40.amzn1.x86_64 mysql55-common-5.5.36-1.44.amzn1.x86_64 is a duplicate with mysql55-common-5.5.34-1.40.amzn1.x86_64 mysql55-libs-5.5.36-1.44.amzn1.x86_64 is a duplicate with mysql55-libs-5.5.34-1.40.amzn1.x86_64 mysql55-server-5.5.36-1.44.amzn1.x86_64 is a duplicate with mysql55-server-5.5.34-1.40.amzn1.x86_64 nss-util-3.15.3-1.19.amzn1.x86_64 is a duplicate with nss-util-3.15.3-1.18.amzn1.x86_64 numactl-2.0.7-8.11.amzn1.x86_64 is a duplicate with numactl-2.0.7-6.10.amzn1.x86_64 1:openssl-1.0.1g-1.69.amzn1.x86_64 is a duplicate with 1:openssl-1.0.1e-4.55.amzn1.x86_64 pam-1.1.8-1.25.amzn1.x86_64 is a duplicate with pam-1.1.1-13.20.amzn1.x86_64 4:perl-5.16.3-280.36.amzn1.x86_64 is a duplicate with 4:perl-5.10.1-136.21.amzn1.x86_64 perl-DBD-MySQL-4.023-2.16.amzn1.x86_64 is a duplicate with perl-DBD-MySQL-4.020-2.8.amzn1.x86_64 perl-DBI-1.627-1.7.amzn1.x86_64 is a duplicate with perl-DBI-1.609-4.4.amzn1.x86_64 1:perl-Digest-SHA-5.85-1.4.amzn1.x86_64 is a duplicate with 1:perl-Digest-SHA-5.47-136.21.amzn1.x86_64 perl-Digest-SHA1-2.13-7.6.amzn1.x86_64 is a duplicate with perl-Digest-SHA1-2.12-2.4.amzn1.x86_64 perl-Encode-Locale-1.03-4.7.amzn1.noarch is a duplicate with perl-Encode-Locale-1.02-3.1.amzn1.noarch perl-HTML-Tagset-3.20-14.6.amzn1.noarch is a duplicate with perl-HTML-Tagset-3.20-4.4.amzn1.noarch perl-LWP-MediaTypes-6.02-1.8.amzn1.noarch is a duplicate with perl-LWP-MediaTypes-6.01-3.3.amzn1.noarch 1:perl-Module-Pluggable-4.8-1.2.amzn1.noarch is a duplicate with 1:perl-Module-Pluggable-3.90-136.21.amzn1.x86_64 perl-Net-LibIDN-0.12-13.5.amzn1.x86_64 is a duplicate with perl-Net-LibIDN-0.12-3.2.amzn1.x86_64 1:perl-Pod-Escapes-1.04-280.36.amzn1.noarch is a duplicate with 1:perl-Pod-Escapes-1.04-136.21.amzn1.x86_64 1:perl-Pod-Simple-3.28-3.5.amzn1.noarch is a duplicate with 1:perl-Pod-Simple-3.13-136.21.amzn1.x86_64 1:perl-TimeDate-2.30-1.6.amzn1.noarch is a duplicate with 1:perl-TimeDate-1.16-11.1.4.amzn1.noarch perl-URI-1.60-8.7.amzn1.noarch is a duplicate with perl-URI-1.40-2.5.amzn1.noarch perl-XML-NamespaceSupport-1.11-9.7.amzn1.noarch is a duplicate with perl-XML-NamespaceSupport-1.10-3.5.amzn1.noarch 4:perl-libs-5.16.3-280.36.amzn1.x86_64 is a duplicate with 4:perl-libs-5.10.1-136.21.amzn1.x86_64 perl-podlators-2.5.1-2.7.amzn1.noarch has installed conflicts perl < ('4', '5.16.1', '234'): 4:perl-5.10.1-136.21.amzn1.x86_64 3:perl-version-0.99.02-2.5.amzn1.x86_64 is a duplicate with 3:perl-version-0.77-136.21.amzn1.x86_64 psmisc-22.20-6.11.amzn1.x86_64 is a duplicate with psmisc-22.6-15.8.amzn1.x86_64 pyliblzma-0.5.3-3.6.amzn1.x86_64 is a duplicate with pyliblzma-0.5.3-3.4.amzn1.x86_64 python26-2.6.9-1.46.amzn1.x86_64 is a duplicate with python26-2.6.9-1.43.amzn1.x86_64 python26-libs-2.6.9-1.46.amzn1.x86_64 is a duplicate with python26-libs-2.6.9-1.43.amzn1.x86_64 readline-6.2-6.13.amzn1.x86_64 is a duplicate with readline-6.0-4.12.amzn1.x86_64 rpm-4.11.2-2.54.amzn1.x86_64 is a duplicate with rpm-4.11.1-3.49.amzn1.x86_64 rpm-build-libs-4.11.2-2.54.amzn1.x86_64 is a duplicate with rpm-build-libs-4.11.1-3.49.amzn1.x86_64 rpm-libs-4.11.2-2.54.amzn1.x86_64 is a duplicate with rpm-libs-4.11.1-3.49.amzn1.x86_64 rpm-python-4.11.2-2.54.amzn1.x86_64 is a duplicate with rpm-python-4.11.1-3.49.amzn1.x86_64 rsyslog-5.8.10-8.25.amzn1.x86_64 is a duplicate with rsyslog-5.8.10-7.24.amzn1.x86_64 sqlite-3.7.17-1.9.amzn1.x86_64 is a duplicate with sqlite-3.6.20-1.8.amzn1.x86_64 system-release-2014.03-2.0.noarch is a duplicate with system-release-2013.09-1.0.noarch sysvinit-2.87-5.dsf.14.amzn1.x86_64 has installed conflicts util-linux < ('0', '2.23.2', None): util-linux-ng-2.17.2-13.17.amzn1.x86_64 sysvinit-2.87-5.dsf.14.amzn1.x86_64 is a duplicate with sysvinit-2.87-4.dsf.10.amzn1.x86_64 tcp_wrappers-7.6-75.11.amzn1.x86_64 is a duplicate with tcp_wrappers-7.6-57.9.amzn1.x86_64 tcp_wrappers-libs-7.6-75.11.amzn1.x86_64 is a duplicate with tcp_wrappers-libs-7.6-57.9.amzn1.x86_64 tzdata-2013i-2.23.amzn1.noarch is a duplicate with tzdata-2013c-2.18.amzn1.noarch tzdata-java-2013i-2.23.amzn1.noarch is a duplicate with tzdata-java-2013c-2.18.amzn1.noarch udev-173-4.13.amzn1.x86_64 is a duplicate with udev-173-4.12.amzn1.x86_64 upstart-0.6.5-13.3.13.amzn1.x86_64 is a duplicate with upstart-0.6.5-12.10.amzn1.x86_64 util-linux-2.23.2-6.21.amzn1.x86_64 has installed conflicts coreutils < ('0', '8.20', None): coreutils-8.4-31.20.amzn1.x86_64 util-linux-2.23.2-6.21.amzn1.x86_64 has installed conflicts sysvinit < ('0', '2.87', '5'): upstart-0.6.5-12.10.amzn1.x86_64, sysvinit-2.87-4.dsf.10.amzn1.x86_64 2:vim-common-7.4.027-2.28.amzn1.x86_64 is a duplicate with 2:vim-common-7.2.411-1.8.17.amzn1.x86_64 2:vim-minimal-7.4.027-2.28.amzn1.x86_64 is a duplicate with 2:vim-minimal-7.2.411-1.8.17.amzn1.x86_64 xz-5.1.2-5alpha.10.amzn1.x86_64 is a duplicate with xz-4.999.9-0.3.beta.20091007git.8.amzn1.x86_64 xz-libs-5.1.2-5alpha.10.amzn1.x86_64 is a duplicate with xz-libs-4.999.9-0.3.beta.20091007git.8.amzn1.x86_64 xz-lzma-compat-5.1.2-5alpha.10.amzn1.x86_64 is a duplicate with xz-lzma-compat-4.999.9-0.3.beta.20091007git.8.amzn1.x86_64 yum-3.4.3-137.51.amzn1.noarch is a duplicate with yum-3.4.3-111.46.amzn1.noarch yum-plugin-priorities-1.1.31-18.17.amzn1.noarch is a duplicate with yum-plugin-priorities-1.1.31-17.16.amzn1.noarch yum-plugin-upgrade-helper-1.1.31-18.17.amzn1.noarch is a duplicate with yum-plugin-upgrade-helper-1.1.31-17.16.amzn1.noarch

*Note: I barely know what I'm doing here, as such this may be incredibly obvious, but I wasn't able to find what I was after on Google.* *Running CentOS 6.7* Yesterday I followed [this guide to set up opendkim](https://www.howtoforge.com/set-up-dkim-domainkeys-identified-mail-working-with-postfix-on-centos-using-opendkim) on my server, and as far as I can tell it is working. This guide told me to get the opendkim package via wget http://sourceforge.net/projects/opendkim/files/opendkim-2.4.2.tar.gz along with tar zxvf opendkim-2.4.2.tar.gz cd opendkim-2.4.2 ./configure --sysconfdir=/etc --prefix=/usr/local --localstatedir=/var make make install I've since found out this is not the latest version (I know I should have checked that first -__-). I found an updated version of the guide showing this can now be installed via yum install opendkim. I would like to move to using that method, but I don't know enough about this stuff to know if that will overwrite things cleanly - or even at all. **What's the safest/best way to install opendkim with yum while removing/overwriting the manual installation** (while keeping my configuration ideally - but that can be redone if necessary)

I am trying to install centos-release-SCL on CentOS 6.7. I want to do this to get python2.7. I have tried: sudo yum --disablerepo=\* --enablerepo=extras install centos-release-SCL Loaded plugins: fastestmirror, refresh-packagekit, security Setting up Install Process Loading mirror speeds from cached hostfile * extras: anorien.csc.warwick.ac.uk No package centos-release-SCL available. Error: Nothing to do I have then tried: sudo yum --disablerepo=\* --enablerepo=extras list available Loaded plugins: fastestmirror, refresh-packagekit, security Loading mirror speeds from cached hostfile * extras: anorien.csc.warwick.ac.uk Available Packages bakefile.i686 0.2.8-3.el6.centos extras centos-release-cr.i686 10:6-0.el6.centos extras centos-release-virt-common.noarch 1-1.el6.centos extras cloud-init.i686 0.7.5-10.el6.centos.2 extras epel-release.noarch 6-8 extras jfsutils.i686 1.1.13-9.el6 extras ldns.i686 1.6.16-7.el6.1 extras ldns-devel.i686 1.6.16-7.el6.1 extras ldns-doc.noarch 1.6.16-7.el6.1 extras ldns-python.i686 1.6.16-7.el6.1 extras opennx.i686 0.16-724.el6.centos.1 extras pytest.noarch 2.3.5-3.el6.centos extras python-backports.i686 1.0-3.el6.centos extras python-backports-ssl_match_hostname.noarch 3.4.0.2-4.el6.centos extras python-boto.noarch 2.32.1-1.el6.centos extras python-chardet.noarch 2.0.1-1.el6.centos extras python-empy.noarch 3.3-5.el6.centos extras python-jsonpatch.noarch 1.2-2.el6.centos extras python-jsonpointer.noarch 1.0-3.el6.centos extras python-oauth.noarch 1.0.1-1.el6.centos extras python-ordereddict.noarch 1.1-2.el6.centos extras python-prettytable.noarch 0.7.2-1.el6.centos extras python-py.noarch 1.4.18-1.el6.centos extras python-requests.noarch 1.1.0-4.el6.centos extras python-six.noarch 1.7.3-1.el6.centos extras python-sphinx10.noarch 1.0.8-1.el6.centos extras python-sphinx10-doc.noarch 1.0.8-1.el6.centos extras python-tornado.noarch 2.2.1-1.el6.centos extras python-tornado-doc.noarch 2.2.1-1.el6.centos extras python-urllib3.noarch 1.5-7.el6.centos extras unbound.i686 1.4.20-23.el6.1 extras unbound-devel.i686 1.4.20-23.el6.1 extras unbound-libs.i686 1.4.20-23.el6.1 extras unbound-python.i686 1.4.20-23.el6.1 extras wxBase.i686 2.8.12-1.el6.centos extras wxGTK.i686 2.8.12-1.el6.centos extras wxGTK-devel.i686 2.8.12-1.el6.centos extras wxGTK-gl.i686 2.8.12-1.el6.centos extras wxGTK-media.i686 2.8.12-1.el6.centos extras Why is centos-release-SCL not available?

I am trying to get the latest release number of the package and not the latest version from the repo. For example

yum --showduplicates list package

Installed Packages
package                    2.1.0-1 
Available Packages
package                    2.1.0-1
package                    2.1.0-2
package                    3.1.0-1

I want to update the existing package to 2.1.0-2 and not to the latest 3.1.0-1. The yum update always try to update to the latest 3.1.0-1. I am writing a script that checks if the release number (in this case 2.1.0-2) is higher than 2.1.0-1 and update to that version.

My centos version is 7.1.1503. When I tried installing yum-utils using yum-install it's trying the repo http://centos.myfahim.com/centos/7.4.1708/os/x86_64/repodata/repomd.xml and other mirrors on centos version 7.4.1708 and got failed. While debugging its mentioned centos 7.4.1708 is deprecated and recommended to go with 7 instead. Why it's trying with centos 7.4.1708 instead of 7.1 and how to fix this?

How to upgrade ruby to a new version in RHEL. When I try - sudo yum install ruby It says > Package ruby-2.0.0.648-33.el7_4.x86_64 already installed and latest > > version Nothing to do When I try - sudo yum install @ruby2.5 It says, > Loaded plugins: fastestmirror, langpacks Repository 'UIM_install' is > > missing name in configuration, using id Repository 'debug' is missing > > name in configuration, using id Repository nodesource is listed more > > than once in the configuration Repository nodesource-source is listed > > more than once in the configuration Repository 'opencl' is missing > > name in configuration, using id Loading mirror speeds from cached > > hostfile Group ruby2.5 does not exist. Error: Nothing to do I need the latest ruby in my system. What is the solution? Edit: I tried sudo yum update ruby and gave the following response. > Loading mirror speeds from cached hostfile > > No packages marked for update

I get the following error: Loaded plugins: langpacks, ulninfo http://yum.oracle.com/repo/OracleLinux/OL7/latest/x86_64/repodata/repomd.xml : [Errno 14] curl#6 - "Could not resolve host: yum.oracle.com; Unknown error" Trying other mirror. failure: repodata/repomd.xml from ol7_latest: [Errno 256] No more mirrors to try. http://yum.oracle.com/repo/OracleLinux/OL7/latest/x86_64/repodata/repomd.xml : [Errno 14] curl#6 - "Could not resolve host: yum.oracle.com; Unknown error" Not sure what exactly this means. Can someone please give me pointers?

Is there a way to tell yum to install a package, selecting a version of that package that would be satisfied by currently installed dependencies? For example, if I'm installing a pecl package and I currently have installed php-5.4.11 but a newer php-5.4.14 is available. Rather than install the new package (and update all php packages to 5.4.14) I just want it to select an older version of the package I requested to be installed without updating all the others (or fail if this cannot be done). This is a specific case in which I know I could exclude or fix the php package but I'm looking for a generic option that would apply to any install. Something like: yum install php-pecl-xxxx --no-updates

Since a couple of days, I'm unable to retrieve repositories data with Yum, in my CentOS 6.5 server. I did yum clean all a dozen of times, it emptied all but didn't solved the problem. I tried to retrieve things by restricting to the single base repo : [base] name=CentOS-$releasever - Base mirrorlist=http://mirrorlist.centos.org/?release=$releasever&arch=$basearch&repo=os gpgcheck=1 gpgkey=file:///etc/pki/rpm-gpg/RPM-GPG-KEY-CentOS-6 yum --verbose update results in : Loading "fastestmirror" plugin Loading "priorities" plugin Config time: 0.010 Yum Version: 3.2.29 Setting up Package Sacks Determining fastest mirrors Could not retrieve mirrorlist http://mirrorlist.centos.org/?release=6&arch=x86_64&repo=os error was 14: PYCURL ERROR 22 - "The requested URL returned error: 403 Forbidden" Error: Cannot find a valid baseurl for repo: base And when I configure a baseurl instead of a mirrorlist, I get this : Loading "fastestmirror" plugin Loading "priorities" plugin Config time: 0.010 Yum Version: 3.2.29 Setting up Package Sacks Determining fastest mirrors http://mirror.centos.org/centos/6/os/x86_64/repodata/repomd.xml : [Errno 14] PYCURL ERROR 22 - "The requested URL returned error: 404 Not Found" Trying other mirror. Error: Cannot retrieve repository metadata (repomd.xml) for repository: base. Please verify its path and try again The server pings mirror.centos.org and I can reach without any problem the mirrorlist and the repomd.xml in a web browser. Disabling the plugins changed nothing. The mirrorlist gives a 403 error and a baseurl 404... rpm -q --verify -f /etc/yum.repos.d/* results in : S.5....T. c /etc/issue .......T. c /etc/yum.repos.d/CentOS-Base.repo .......T. c /etc/yum.repos.d/CentOS-Debuginfo.repo .......T. c /etc/yum.repos.d/CentOS-Media.repo .......T. c /etc/yum.repos.d/CentOS-Vault.repo S.5....T. c /etc/issue .......T. c /etc/yum.repos.d/CentOS-Base.repo .......T. c /etc/yum.repos.d/CentOS-Debuginfo.repo .......T. c /etc/yum.repos.d/CentOS-Media.repo .......T. c /etc/yum.repos.d/CentOS-Vault.repo S.5....T. c /etc/issue .......T. c /etc/yum.repos.d/CentOS-Base.repo .......T. c /etc/yum.repos.d/CentOS-Debuginfo.repo .......T. c /etc/yum.repos.d/CentOS-Media.repo .......T. c /etc/yum.repos.d/CentOS-Vault.repo S.5....T. c /etc/issue .......T. c /etc/yum.repos.d/CentOS-Base.repo .......T. c /etc/yum.repos.d/CentOS-Debuginfo.repo .......T. c /etc/yum.repos.d/CentOS-Media.repo .......T. c /etc/yum.repos.d/CentOS-Vault.repo .......T. c /etc/yum.repos.d/epel-testing.repo .......T. c /etc/yum.repos.d/epel.repo .......T. c /etc/yum.repos.d/epel-testing.repo .......T. c /etc/yum.repos.d/epel.repo le fichier /etc/yum.repos.d/isv:ownCloud:community.repo n'appartient à aucun paquetage .......T. c /etc/yum.repos.d/jpackage.repo le fichier /etc/yum.repos.d/jpackage.repo.rpmsave n'appartient à aucun paquetage « n'appartient à aucun paquetage » means « doesn't belong to any package », in french... Those problems occur with whatever repo I enable/disable.

In a moment of confusion and impatience, I severely damaged my OS. Here's the deal... **System**: CentOS 7 **Problem**: essential packages like SAMBA do not work, and yum will not do anything. **How it started**: I installed kmod-xpad, which required a kernel update. This new kernel never worked, but I could boot from the old kernel on the boot loader. I did a routine package update via yum. Later on, I tried to remove kmod-xpad, but that failed. Now the system permanently tells me that I need to restart in order to install updates. Even worse, I cannot mount a network drive via Samba. I get an error message like... /sbin/mount.cifs: /usr/lib64/samba/libreplace.so: version SAMBA_4.1.1' not found (required by /lib64/libwbclient.so.0) /sbin/mount.cifs: /usr/lib64/samba/libwinbind-client.so: version `SAMBA_4.1.1' not found (required by /lib64/libwbclient.so.0) While trying to fix SAMBA, I found that yum is completely confused, and had unfinished transactions. I searched around for solutions without luck (e.g. such as https://unix.stackexchange.com/questions/127929/why-does-yum-update-fails-with-many-duplicates-after-many-months-of-no-upgrad) **Yum error messages**: When I run yum clean all and yum update I run into an error with dependency resolution, and am then told that there are 374 pre-existing rpmdb problems, which are basically a bunch of duplicate packages. Here is a snippet: --> Finished Dependency Resolution Error: Package: avahi-libs-0.6.31-13.el7.x86_64 (@anaconda) Requires: avahi = 0.6.31-13.el7 Removing: avahi-0.6.31-13.el7.x86_64 (@anaconda) avahi = 0.6.31-13.el7 Updated By: avahi-0.6.31-14.el7.x86_64 (base) avahi = 0.6.31-14.el7 Error: avahi-libs conflicts with avahi-0.6.31-14.el7.x86_64 Error: avahi-autoipd conflicts with avahi-0.6.31-14.el7.x86_64 ... You could try using --skip-broken to work around the problem ** Found 374 pre-existing rpmdb problem(s), 'yum check' output follows: 1:NetworkManager-1.0.0-14.git20150121.b4ea599c.el7.x86_64 is a duplicate with 1:NetworkManager-0.9.9.1-29.git20140326.4dba720.el7_0.x86_64 ... avahi-libs-0.6.31-14.el7.x86_64 is a duplicate with avahi-libs-0.6.31-13.el7.x86_64 avahi-ui-gtk3-0.6.31-14.el7.x86_64 has installed conflicts avahi This sounds tedious, and I'm not confident that it will really resolve my problem. Is this a situation that calls for reinstallation? Any advice will be appreciated.

We are trying to install a package from an internal mirror of the EPEL repository. When we do so, we get the following error message:

epel/primary_db            FAILED
https://yum.example.com/yum/EPEL/7/x86_64/repodata/cee535f542076e9b28a71100daf379d696383d5628fdd4571f37dae6f918d0cf0-primary.sqlite.bz2 : [Errno 14] HTTPS Error 404 - Not Found
Trying other mirror
https://yum.example.com/yum/EPEL/7/x86_64/repodata/cee535f542076e9b28a71100daf379d696383d5628fdd4571f37dae6f918d0cf0-primary.sqlite.bz2 : [Errno 14] HTTPS Error 404 - Not Found
Trying other mirror


 One of the configured repositories failed (epel),
 and yum doesn't have enough cached data to continue. At this point, the only
 safe thing yum can do is fail. There are a few ways to work "fix" this:


failure: repodata/cee535f542076e9b28a71100daf379d696383d5628fdd4571f37dae6f918d0cf0-primary.sqlite.bz2 from epel: [Errno 256] No more mirrors to try.
https://yum.example.com/yum/EPEL/7/x86_64/repodata/cee535f542076e9b28a71100daf379d696383d5628fdd4571f37dae6f918d0cf0-primary.sqlite.bz2 : [Errno 14] HTTPS Error 404 - Not Found

Looking at yum.example.com/yum/EPEL/7/x86_64/repodata/ in a browser, we see entries for 73d6...46bd-primary.sqlite.bz2 and af97...d886-primary.sqlite.bz2; however, there is no entry for cee5...0cf0-primary.sqlite.bz2. How do we fix this issue? --- The following are the full contents of /etc/yum.repos.d/epel.repo: ``` [epel] sslverify=0 description=Extra Packages for Enterprise Linux $releasever - $basearch baseurl=https://yum.example.com/yum/EPEL/$releasever/$basearch gpgcheckk=0 name=epel

# yum list updates Loaded plugins: langpacks, product-id, search-disabled-repos, subscription-manager This system is not registered to Red Hat Subscription Management. You can use subscription-manager to register. One of the configured repositories failed (Unknown), and yum doesn't have enough cached data to continue. At this point the only safe thing yum can do is fail. There are a few ways to work "fix" this: 1. Contact the upstream for the repository and get them to fix the problem. 2. Reconfigure the baseurl/etc. for the repository, to point to a working upstream. This is most often useful if you are using a newer distribution release than is supported by the repository (and the packages for the previous distribution release still work). 3. Run the command with the repository temporarily disabled yum --disablerepo= ... 4. Disable the repository permanently, so yum won't use it by default. Yum will then just ignore the repository until you permanently enable it again or use --enablerepo for temporary usage: yum-config-manager --disable or subscription-manager repos --disable= 5. Configure the failing repository to be skipped, if it is unavailable. Note that yum will try to contact the repo. when it runs most commands, so will have to try and fail each time (and thus. yum will be much slower). If it is a very temporary problem though, this is often a nice compromise: yum-config-manager --save --setopt=.skip_if_unavailable=true