Bug 178840 – media-libs/libkexiv2-0.1.2 version bump

• Status: RESOLVED FIXED
• Product: Gentoo Linux

[Description Łukasz Mierzwa 2007-05-17 07:55:00 UTC]

New version:
added support for exiv2 from svn (next 0.14.0 release) 
API changed: 
added printExiv2ExceptionError to manage Exiv2 C++ Exception error message

Reproducible: Always

[Comment 1 Carsten Lohrke (RETIRED) 2007-05-17 10:19:15 UTC]

*** Bug 178850 has been marked as a duplicate of this bug. ***

[Comment 2 Jonathan Heaney 2007-05-17 16:10:19 UTC]

The ebuild for this is so simple a quick version bump into your portage overlay is enough to fix it.

Hmm - kipi-plugins fails to build now ... I don't know if this is because of the exiv2 or libkexiv2 bumps.

[Comment 3 Łukasz Mierzwa 2007-05-17 16:21:06 UTC]

(In reply to comment #2)
> The ebuild for this is so simple a quick version bump into your portage overlay
> is enough to fix it.
For me sure, for other users it would be better to have it in portage.

> Hmm - kipi-plugins fails to build now ... I don't know if this is because of
> the exiv2 or libkexiv2 bumps.
I build kipi-plugins with libkexiv-0.1.2 but latest exiv made kipi-plugins and digikam to fail during compilation.

[Comment 4 Roberto Castagnola 2007-05-18 07:19:56 UTC]

Simply renaming the ebuild worked for me (~x86)

Further I changed RDEPEND to
RDEPEND=">=media-gfx/exiv2-0.14"

[Comment 5 Guillaume Castagnino 2007-05-18 07:45:02 UTC]

(In reply to comment #3)
> (In reply to comment #2)
> > Hmm - kipi-plugins fails to build now ... I don't know if this is because of
> > the exiv2 or libkexiv2 bumps.
> I build kipi-plugins with libkexiv-0.1.2 but latest exiv made kipi-plugins and
> digikam to fail during compilation.
> 

Yes, to build against exiv2-0.14 :
- digikam needs to be updated to 0.9.2-beta1 (that remove direct dependancy to exiv2, using only libkexiv2)
- kipi-plugins needs to be updated to a svn snapshot : the lastest released version do not manage exiv2-0.14 changes...

[Comment 6 Łukasz Mierzwa 2007-05-18 07:52:36 UTC]

So gentoo devs should mask exiv-0.14 until other apps like kipi-plugins are updated or provide kipi-plugins svn snapshot. Am I right?

[Comment 7 Roberto Castagnola 2007-05-18 08:57:24 UTC]

(In reply to comment #4)
> Further I changed RDEPEND to
> RDEPEND=">=media-gfx/exiv2-0.14"

After checking changes in libkexiv2-0.1.2/libkexiv2/kexiv2.cpp, I found out that it should still compile against <media-gfx/exiv2-0.14 (not tested), so my RDEPEND change is probably not required.


(In reply to comment #5)
> Yes, to build against exiv2-0.14 :
> - digikam needs to be updated to 0.9.2-beta1 (that remove direct dependancy to
> exiv2, using only libkexiv2)
> - kipi-plugins needs to be updated to a svn snapshot : the lastest released
> version do not manage exiv2-0.14 changes...

In exiv-0.14 only signature of AnyError::what() is changed (no other API changes); now it return
  const char*
instead of
  std::string

So digikam-0.9.1 and kipi-plugins-0.1.3 can be easily patched to compile against exiv-0.14 (see bug 178939 and bug 178942)

[Comment 8 Jonathan Heaney 2007-05-19 15:07:52 UTC]

(In reply to comment #7)

Thanks Roberto, the patches you've linked to work for me here on ~x86.

[Comment 9 Peter Volkov (RETIRED) 2007-05-20 08:22:03 UTC]

media-libs/libkexiv2-0.1.5 in portage.