search for: exiv2

...ta and Security Advisory 2019:2101 Low Upstream details at : https://access.redhat.com/errata/RHSA-2019:2101 The following updated files have been uploaded and are currently syncing to the mirrors: ( sha256sum Filename ) x86_64: dbfa835039594a636a9188545655af04b0e9fd51698aa498487d0b584cb89ddc exiv2-0.27.0-2.el7_6.x86_64.rpm 355b07ff722e13d13cb5b6cfba9daa18b590c9da267ee3aac36ad11aa26312ab exiv2-devel-0.27.0-2.el7_6.i686.rpm ff1d7dad703184a9d60eda2b3eadf154280a133ba3f07ea038291c074b855ee9 exiv2-devel-0.27.0-2.el7_6.x86_64.rpm 01f4532fe90d7ef8e768573d0022035a04e7af27004ff96168a9c8c2479724e4 e...

For some time now updates on my CentOS box had skipped exiv2. Yesterday I decided to do something about it, so I removed it - together with gwenview, digikam and, IIRC, libexiv2. That sounded reasonable, so I accepted the removal, then re-installed gwenview and digikam, which, of course, pulled in the two exiv2 packages. The version number of exiv2 so...

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 somewher...

...> 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

...currently installing a dozen CentOS 7 + KDE desktops in our local school. I've already installed a minimal X11 + WindowMaker, and now I want to install KDE on top of that, but the installation fails. There's some broken dependency in the repos. I've narrowed the problem down to the libkexiv2 package. Here's that I get. # yum install libkexiv2 ... --> Running transaction check ---> Package kde-l10n.noarch 0:4.10.5-2.el7 will be installed ---> Package libkexiv2.x86_64 0:4.10.5-4.el7 will be installed --> Processing Dependency: libexiv2.so.26()(64bit) for package: libkexi...

Hello, since today I could not update my CentOS 5.3 system with yum cause of the following error message. # yum update [...] Resolving Dependencies --> Running transaction check ---> Package exiv2.i386 0:0.18.2-1.el5.rf set to be updated ---> Package perl-Params-Util.i386 0:1.00-1.el5.rf set to be updated ---> Package perl-Moose.noarch 0:0.86-1.el5.rf set to be updated --> Processing Dependency: perl(Class::MOP) >= 0.89 for package: perl-Moose ---> Package perl-MRO-Compat.noar...

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

Le 16/05/2018 ? 17:26, James Pearson a ?crit?: > 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? It looks like the problem is solved. I just installed Digikam, and it went fine, without any extra -compat packages. -- Microlinux - Solutions informatiques durables 7, place de l'?glise - 30730 Montpezat Site : https://www.mi...

Le 02/05/2019 ? 13:59, Nicolas Kovacs a ?crit?: > # yum install libkexiv2 > ... > --> Running transaction check > ---> Package kde-l10n.noarch 0:4.10.5-2.el7 will be installed > ---> Package libkexiv2.x86_64 0:4.10.5-4.el7 will be installed > --> Processing Dependency: libexiv2.so.26()(64bit) for package: > libkexiv2-4.10.5-4.el7.x86_64 >...

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)