i try to update server thru yum clean all && yum update command, but got strange:
...
Loaded plugins: fastestmirror
...
--> Processing Dependency: /usr/sbin/ldconfig for package: libxvidcore4-1.3.2-15.el7.x86_64
--> Processing Dependency: /usr/sbin/ldconfig for package: libxvidcore4-1.3.2-15.el7.x86_64
--> Finished Dependency Resolution
Error: Package: libxvidcore4-1.3.2-15.el7.x86_64 (@Kaltura)
Requires: /usr/sbin/ldconfig
Removing: glibc-2.17-78.el7.i686 (@base)
Not found
Updated By: glibc-2.17-106.el7_2.4.i686 (updates)
Not found
You could try using --skip-broken to work around the problem
You could try running: rpm -Va --nofiles --nodigest
Start by removing all Kaltura packages with:
# yum remove “kaltura” -y
the try:
# yum update
and update all packages including glibc to the latest available.
Hello jess!
i think this is Kaltura rpmbuild problem
i found another bug thread https://bugzilla.redhat.com/show_bug.cgi?id=1063607
see comments #12 and #13
i think libxvidcore4 (provided by Kaltura) should depend on /sbin/ldconfig and not on /usr/sbin/ldconfig
totally uninstalling, upgrading and reinstalling Kaltura packages - bad way.
It is not a Kaltura issue, the libxvidcore4 package is taken from the ATrpms repo as is and is placed in the Kaltura repo to save end users from the need to add that repo. Regardless, different versions of RHEL/CentOS distros place ldconfig in different locations, which is rather stupid but nonetheless true. For instance, on RHEL/CentOS 6, it is under /sbin/ldconfig, whereas, on 7, which is what you have, it is placed under /usr/sbin/ldconfig, further more, it seems the change was made AFTER releasing the first glibc package for RHEL/CentOS 7, glibc is the package that provides the ldconfig util.
Hello @jess
may be remove dep on ldconfig? and retain dep on glibc that contain ldconfig?
no matter whereis ldconfig is (/sbin or /usr/sbin)
/sorry, i’m an ubuntu fan, and do not work with centos since 5.4/
and second think about glibc and updates, i have tried to remove gibc.i686:
Dependencies Resolved
========================================================================================================================================================================
Package Arch Version Repository Size
========================================================================================================================================================================
Removing:
glibc i686 2.17-78.el7 @base 14 M
Removing for dependencies:
kaltura-batch noarch 11.11.0-1 @Kaltura-noarch 30 k
kaltura-mencoder x86_64 3.4.6-9 @Kaltura 44 M
kaltura-server noarch 11.11.0-1 @Kaltura-noarch 0.0
libdv i686 1.0.0-17.el7 @base 169 k
libjpeg-turbo i686 1.2.90-5.el7 @base 361 k
libmng i686 1.0.10-14.el7 @base 523 k
libogg i686 2:1.3.0-7.el7 @base 34 k
liboil i686 0.3.16-10.el7 @base 513 k
libpng12 i686 1.2.50-6.el7 @base 653 k
libstdc++ i686 4.8.5-4.el7 @base 996 k
libtheora i686 1:1.1.1-8.el7 @base 472 k
ncurses-libs i686 5.9-13.20130511.el7 @base 926 k
nss-softokn-freebl i686 3.16.2.3-13.el7_1 @updates 418 k
speex i686 1.2-0.19.rc1.el7 @base 181 k
zlib i686 1.2.7-15.el7 @base 180 k
Transaction Summary
========================================================================================================================================================================
Remove 1 Package (+15 Dependent packages)
Each packaging format has its own conventions, in an RPM spec, it is customary to declare dep on ldconfig in this way.
No point declaring a dep on glibc, since ALL RHEL based distros already include it.
That should be fine now, however, post updating to the package I pushed today.
Also, we DO support both Debian and Ubuntu as well and provide debs for them, if you prefer Ubuntu, why not use that?
Mencoder depends on i686 libs because it has no full port to 64bit. Some of its libs are 32bit only.
--> Processing Dependency: /usr/sbin/ldconfig for package: libxvidcore4-1.3.2-16.x86_64
--> Finished Dependency Resolution
Error: Package: libxvidcore4-1.3.2-16.x86_64 (@Kaltura)
Requires: /usr/sbin/ldconfig
Removing: glibc-2.17-78.el7.i686 (@base)
Not found
Updated By: glibc-2.17-106.el7_2.4.i686 (updates)
Not found
You could try using --skip-broken to work around the problem
You could try running: rpm -Va --nofiles --nodigest
Not sure what the issue might be. Start by making sure:
# rpm -qf /usr/sbin/ldconfig
returns correctly with the glibc package and version.
If it does, then perhaps try to do:
# yum update glibc
manually to see why it is failing and perhaps report to CentOS, as you can see, the complaint is about updating the glibc package, not a Kalturian one.