CentOS-7.4 Elfutils

Home » CentOS » CentOS-7.4 Elfutils
CentOS 3 Comments


I’m taking 7.4 for a spin.  I did the minimal install, and ran into trouble with groupinstall base.  The trouble seems to stem from elfutils.  One command claims elfutils-libs-0.166-2.el7.x86_64 is missing, and another one claims it’s installed.  Not sure what’s going on here.

[root@ip-172-31-34-187 ~]# yum -y install elfutils.x86_64
Loaded plugins: fastestmirror Loading mirror speeds from cached hostfile
 * base: mirror.web-ster.com
 * extras: mirror.chpc.utah.edu
 * updates: mirrors.cat.pdx.edu Resolving Dependencies
–> Running transaction check
—> Package elfutils.x86_64 0:0.166-2.el7 will be installed
–> Processing Dependency: elfutils-libs(x86-64) = 0.166-2.el7 for package: elfutils-0.166-2.el7.x86_64
–> Processing Dependency: elfutils-libelf(x86-64) = 0.166-2.el7 for package: elfutils-0.166-2.el7.x86_64
–> Finished Dependency Resolution Error: Package: elfutils-0.166-2.el7.x86_64 (base)
           Requires: elfutils-libelf(x86-64) = 0.166-2.el7
           Installed: elfutils-libelf-0.168-8.el7.x86_64 (@anaconda)
               elfutils-libelf(x86-64) = 0.168-8.el7
           Available: elfutils-libelf-0.166-2.el7.x86_64 (base)
               elfutils-libelf(x86-64) = 0.166-2.el7
Error: Package: elfutils-0.166-2.el7.x86_64 (base)
           Requires: elfutils-libs(x86-64) = 0.166-2.el7
           Installed: elfutils-libs-0.168-8.el7.x86_64 (@anaconda)
               elfutils-libs(x86-64) = 0.168-8.el7
           Available: elfutils-libs-0.166-2.el7.x86_64 (base)
               elfutils-libs(x86-64) = 0.166-2.el7
 You could try using –skip-broken to work around the problem
 You could try running: rpm -Va –nofiles –nodigest

[root@ip-172-31-34-187 ~]# yum -y install elfutils-libs.x86_64
Loaded plugins: fastestmirror Loading mirror speeds from cached hostfile
 * base: mirror.web-ster.com
 * extras: mirror.chpc.utah.edu
 * updates: mirrors.cat.pdx.edu Package matching elfutils-libs-0.166-2.el7.x86_64 already installed. Checking for update. Nothing to do

3 thoughts on - CentOS-7.4 Elfutils

  • We have not released 7.4.1708 yet .. so the 7/ on all the mirrors still points to 7.3.1611 .. so you can’t really use the default CentOS-Base.repo file for 7.4.1708 yet

    One way is to enable the CR repo (as already pointed out), that has almost all of the 7.4.1708 tree in it (minus anaconda and CentOS-release and their dependencies). That would be the easiest way at this point. It should make most things work. Although, the comps.xml file (the thing that controls group installs) is different between 7.3.1611 and


    If you see a mirror that has 7.4.1708 on it (most, including mirror.CentOS.org don’t and won’t until we complete the release cycle .. sometime later this week, probably Wednesday or Thursday) .. but if you see a mirror with that branch, you can remark out the “mirrorlist=” line and enable the “baseurl=” line in each repo and change the url line to replace /$releasever/ to /7.4.1708/ on each of the baseurl ..


    You can wait until we actually release 7.4.1708. It would be best if you waited .. because:

    We still need to give the Special Interest Groups (SIGs), via the Community Build System (https://cbs.CentOS.org/) and the CI system
    (https://ci.CentOS.org) access to 7.4.1708 so that they can make sure this release works with their software.

    If we have any issues found in that process, we may still submit changes to the 7.4.1708 tree, so the ones that exist now MAY NOT be the final tree, we are just trying to sync out what we have to mirrors so the final tree will not take so long to sync later.

    We are syncing the current tree out at ‘chmod 700’ .. so the only way it would be visible is if the user used to sync the tree was also the owner of the httpd process. Just to reiterate, that tree may not be the final tree, but it should be very, very close.

    We will announce (on this mailing list and the CentOS-announce mailing list) when the 7.4.1708 tree has been fully tested and usable.

    Thanks, Johnny Hughes

  • Note: if you make these changes, you will need to change it back after we release the 7.4.1708 tree, OR you will be stuck on the 7.4.1708 tree as long as you have these changes in place. That will mean your yum will stop working when we release the next point release (based on RHEL
    7.5 source code) in the future.