CentOS - May 2018 - Problem with Digikam and libgphoto2 after latest update

Hi,

I have CentOS 7 with KDE on my workstation. I'm using the CR repo. I had
to remove Digikam to be able to do the latest update (1 GB of updates...
wow). Here's what happens when I try to reinstall it.

# yum install digikam
...
--> Finished Dependency Resolution
Error: Package: digikam-4.10.0-6.el7.x86_64 (epel)
           Requires: libgphoto2_port.so.10(LIBGPHOTO2_5_0)(64bit)
           Available: libgphoto2-2.5.2-5.el7.x86_64 (base)
               libgphoto2_port.so.10(LIBGPHOTO2_5_0)(64bit)
           Installed: libgphoto2-2.5.15-1.el7.x86_64 (@cr)
              ~libgphoto2_port.so.12(LIBGPHOTO2_5_0)(64bit)
Error: Package: digikam-4.10.0-6.el7.x86_64 (epel)
           Requires: libgphoto2_port.so.10()(64bit)
           Available: libgphoto2-2.5.2-5.el7.x86_64 (base)
               libgphoto2_port.so.10()(64bit)
           Installed: libgphoto2-2.5.15-1.el7.x86_64 (@cr)
              ~libgphoto2_port.so.12()(64bit)
 You could try using --skip-broken to work around the problem
 You could try running: rpm -Va --nofiles --nodigest

Any suggestions? Just wait until the EPEL maintainers rebuild it against
the latest stuff?

Cheers,

Niki
-- 
Microlinux - Solutions informatiques durables
7, place de l'?glise - 30730 Montpezat
Site : https://www.microlinux.fr
Blog : https://blog.microlinux.fr
Mail : info at microlinux.fr
T?l. : 04 66 63 10 32

On 28/04/18 21:23, Nicolas Kovacs wrote:
> Hi,
> 
> I have CentOS 7 with KDE on my workstation. I'm using the CR repo. I
had
> to remove Digikam to be able to do the latest update (1 GB of updates...
> wow). Here's what happens when I try to reinstall it.
> 
> # yum install digikam
> ...
> --> Finished Dependency Resolution
> Error: Package: digikam-4.10.0-6.el7.x86_64 (epel)
>            Requires: libgphoto2_port.so.10(LIBGPHOTO2_5_0)(64bit)
>            Available: libgphoto2-2.5.2-5.el7.x86_64 (base)
>                libgphoto2_port.so.10(LIBGPHOTO2_5_0)(64bit)
>            Installed: libgphoto2-2.5.15-1.el7.x86_64 (@cr)
>               ~libgphoto2_port.so.12(LIBGPHOTO2_5_0)(64bit)
> Error: Package: digikam-4.10.0-6.el7.x86_64 (epel)
>            Requires: libgphoto2_port.so.10()(64bit)
>            Available: libgphoto2-2.5.2-5.el7.x86_64 (base)
>                libgphoto2_port.so.10()(64bit)
>            Installed: libgphoto2-2.5.15-1.el7.x86_64 (@cr)
>               ~libgphoto2_port.so.12()(64bit)
>  You could try using --skip-broken to work around the problem
>  You could try running: rpm -Va --nofiles --nodigest
> 
> Any suggestions? Just wait until the EPEL maintainers rebuild it against
> the latest stuff?
> 
> Cheers,
> 
> Niki
> 
Yes, that's something we discovered during CR QA tests on our nodes :
people relying on third-party repositories will get such kind of errors
and so will have to contact upstream maintainers to rebuild against
$current release. Same issue with libgphoto : wine has to be rebuilt too
(unsigned pkgs available here :
https://people.centos.org/arrfab/CentOS7/wine32bits/)

-- 
Fabian Arrotin
The CentOS Project | https://www.centos.org
gpg key: 56BEC54E | twitter: @arrfab

-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 198 bytes
Desc: OpenPGP digital signature
URL:
<http://lists.centos.org/pipermail/centos/attachments/20180429/57ccbcf9/attachment-0001.sig>

Le 29/04/2018 ? 17:52, Fabian Arrotin a ?crit?:
> Yes, that's something we discovered during CR QA tests on our nodes :
> people relying on third-party repositories will get such kind of errors
> and so will have to contact upstream maintainers to rebuild against
> $current release. Same issue with libgphoto : wine has to be rebuilt too
> (unsigned pkgs available here :
> https://people.centos.org/arrfab/CentOS7/wine32bits/)
OK, thanks for the heads-up.

Cheers,

Niki

-- 
Microlinux - Solutions informatiques durables
7, place de l'?glise - 30730 Montpezat
Site : https://www.microlinux.fr
Blog : https://blog.microlinux.fr
Mail : info at microlinux.fr
T?l. : 04 66 63 10 32

Le 29/04/2018 ? 17:52, Fabian Arrotin a ?crit?:
> Yes, that's something we discovered during CR QA tests on our nodes :
> people relying on third-party repositories will get such kind of errors
> and so will have to contact upstream maintainers to rebuild against
> $current release.

There's a similar problem with gthumb and exiv2.

-- 
Microlinux - Solutions informatiques durables
7, place de l'?glise - 30730 Montpezat
Site : https://www.microlinux.fr
Blog : https://blog.microlinux.fr
Mail : info at microlinux.fr
T?l. : 04 66 63 10 32