[CentOS] elrepo problem?

Tue Sep 9 16:11:38 UTC 2014
Ned Slider <ned at unixmail.co.uk>

On 09/09/14 17:02, Les Mikesell wrote:
> On Tue, Sep 9, 2014 at 10:54 AM, Jim Perrin <jperrin at centos.org> wrote:
>> On 09/09/2014 10:49 AM, Les Mikesell wrote:
>>> So much for elrepo being a painless way to get working Nvidia drivers...
>> This isn't elrepo's fault.
>> The glibc update changes the location of the ldconfig binary. It's still
>> in root's path, but anything that had a hardcoded path as a requirement
>> will break.
> Ummm, great...  I thought that was just the sort of breakage that
> 'Enterprise' OS versions were supposed to avoid.  (I realize it's not
> CentOS's fault either).
>> The original glibc package provides both /usr/sbin/ldconfig and
>> /sbin/ldconfig, while the updated package only provides /sbin/ldconfig.
> The whole 's' concept was a bad idea to begin with.  Why did they have
> to make it worse?
>>> Yum update (or just update glibc) says:
>>> --> Processing Dependency: /usr/sbin/ldconfig for package:
>>> nvidia-x11-drv-304xx-304.123-1.el7.elrepo.x86_64
>>> --> Finished Dependency Resolution
>>> Error: Package: nvidia-x11-drv-304xx-304.123-1.el7.elrepo.x86_64 (@elrepo)
>>>            Requires: /usr/sbin/ldconfig
>>>            Removing: glibc-2.17-55.el7.x86_64 (@anaconda)
>>>                Not found
>>>            Updated By: glibc-2.17-55.el7_0.1.x86_64 (updates)
>>>                Not found
>>>  You could try using --skip-broken to work around the problem
>>> What do those 'not found's mean?
>> It means there's no more /usr/sbin/ldconfig provided in the newer packages.
> Seems odd to say it twice.   But what's the right fix here?

Hi Les,

Actually I think Jim is being generous and I do take at least some
responsibility for the breakage.

I've already committed a fix (below) but it won't show up until the next
nvidia legacy driver release:


For now, one workaround is to install the glibc update with --nodeps
(using rpm).