Yum Update Fails With libraw.so.5()(64bit)

[gsownsby]

Hello All,

While doing a "routine" yum update last night, I received the following messages regarding libraw.so.5()(64bit). Any suggestions as to resolving this condition properly? Thank you.

Gary

[root@zeus ~]# yum update
Loaded plugins: fastestmirror, langpacks
Existing lock /var/run/yum.pid: another copy is running as pid 7687.
Another app is currently holding the yum lock; waiting for it to exit...
The other application is: PackageKit
Memory : 257 M RSS (1.5 GB VSZ)
Started: Sat Aug 10 08:59:37 2019 - 00:11 ago
State : Sleeping, pid: 7687
Loading mirror speeds from cached hostfile
* base: bay.uchicago.edu
* epel: mirror.uic.edu
* extras: ftp.ussg.iu.edu
* nux-dextop: mirror.li.nux.ro
* remi-php70: mirror.team-cymru.com
* remi-php71: mirror.team-cymru.com
* remi-php73: mirror.team-cymru.com
* remi-safe: mirror.team-cymru.com
* updates: ftpmirror.your.org
Resolving Dependencies
--> Running transaction check
---> Package LibRaw.x86_64 0:0.14.8-5.el7.20120830git98d925 will be updated
--> Processing Dependency: libraw.so.5()(64bit) for package: libkdcraw-4.10.5-5.el7.x86_64
--> Processing Dependency: libraw.so.5()(64bit) for package: shotwell-0.28.4-1.el7.x86_64
---> Package LibRaw.x86_64 0:0.19.2-0.el7.remi will be an update
--> Finished Dependency Resolution
Error: Package: libkdcraw-4.10.5-5.el7.x86_64 (@base)
Requires: libraw.so.5()(64bit)
Removing: LibRaw-0.14.8-5.el7.20120830git98d925.x86_64 (@anaconda)
libraw.so.5()(64bit)
Updated By: LibRaw-0.19.2-0.el7.remi.x86_64 (remi-safe)
~libraw.so.19()(64bit)
Error: Package: shotwell-0.28.4-1.el7.x86_64 (@anaconda)
Requires: libraw.so.5()(64bit)
Removing: LibRaw-0.14.8-5.el7.20120830git98d925.x86_64 (@anaconda)
libraw.so.5()(64bit)
Updated By: LibRaw-0.19.2-0.el7.remi.x86_64 (remi-safe)
~libraw.so.19()(64bit)
You could try using --skip-broken to work around the problem
** Found 1 pre-existing rpmdb problem(s), 'yum check' output follows:
webmin-1.910-1.noarch has missing requires of perl(Encode::Detect)

[TrevorH]

You're going to want to ask Remi since it's his package that's broken things ...

Updated By: LibRaw-0.19.2-0.el7.remi.x86_64 (remi-safe)
~libraw.so.19()(64bit)

He does sometimes visit this forum buit I think you might get a quicker answer by either asking on his own forum or joining #remirepo on the Freenode IRC channel.

[gsownsby]

Thank you. We'll try contacting him directly.

Gary

[gsownsby]

TrevorH,

No luck contacting Remi. Any other thoughts on resolving this issue?

Thank you.

Gary

[chrismfz]

Without knowing what exactly you did, it seems that libraw is in both centos repo and remi repo.
Did you tried to install yum priorities and give centos repo a priority of 1 and remi 2 ?

(Search for "centos 7 yum priorities" for instructions)

[desertcat]

TrevorH,

No luck contacting Remi. Any other thoughts on resolving this issue?

Thank you.

Gary

Ah!! Another one! Welcome to the club. There are a couple things you can do. For a short time "fix" ( really a work around) run the following command:

yum update --exclude=libraw

CentOS 7.7 will becoming out within the next month or two and various packages are moving to the repos for RHEL 7.7. This may or may not "solve" the problem ... assuming that is the problem to start with. More and more packages are heading in that direction including kmod-nvidia , so now when I run yum update my command line looks like this:

yum update --exclude=kmod-nvidia --exclude=libraw

...and before I start the actual roll-over I might have appended 4-5 more yum update --exclude=xyz packages.

Alternately go to /etc/yum.repos.d and copy the following repos (You will have at least one of the following) to a backup file:

remi-php70.repo
remi-safe.repo
remi.repo

...then DELETE all remi-.repos from /etc/yum.repos.d. Then when CentOS 7.7 does come out simply copy all those repos back into /etc/yum.repos.d. I've done that a number of times. IF this is a remi problem then the new roll over won't fix it, and you will have taken a source of problems out of /etc/yum.repos.d. Currently I've taken a wait and see approach by simply excluding that particular file from the yum update search path.

Hope this helps.

[remirepo]

See https://github.com/remicollet/remirepo/issues/123