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

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

On Tue, May 1, 2018 at 8:25 AM, Nicolas Kovacs <info at microlinux.fr>
wrote:
>
> There's a similar problem with gthumb and exiv2.
This is a known issue and there is a workaround:

https://bugzilla.redhat.com/show_bug.cgi?id=1568618
https://access.redhat.com/discussions/3414821

Akemi

Akemi Yagi wrote:
>>
>> There's a similar problem with gthumb and exiv2.
> 
> This is a known issue and there is a workaround:
> 
> https://bugzilla.redhat.com/show_bug.cgi?id=1568618
> https://access.redhat.com/discussions/3414821
I've just hit this issue - to save me re-inventing the wheel, does a 
'exiv2-libs-compat' (S)RPM exist somewhere that I could get hold of?

Thanks

James Pearson