Bug 178939 - media-gfx/digikam-0.9.1 fails to build with media-gfx/exiv2-0.14
Bug#: 178939 Product:  Gentoo Linux Version: unspecified Platform: All
OS/Version: Linux Status: RESOLVED Severity: normal Priority: P2
Resolution: FIXED Assigned To: kde@gentoo.org Reported By: roberto.castagnola@gmail.com
Component: Ebuilds
URL: 
Summary: media-gfx/digikam-0.9.1 fails to build with media-gfx/exiv2-0.14
Keywords:  
Status Whiteboard: 
Opened: 2007-05-17 21:04 0000
Description:   Opened: 2007-05-17 21:04 0000
Due to API change in exiv2-0.14, media-gfx/digikam fails to build.

------- Comment #1 From Roberto Castagnola 2007-05-17 21:06:41 0000 -------
Created an attachment (id=119556) [details]
digikam-0.9.1-exiv2.patch

patch for digikam-0.9.1 needed to build against media-gfx/exiv2-0.14

------- Comment #2 From Roberto Castagnola 2007-05-17 21:08:16 0000 -------
Created an attachment (id=119557) [details]
digikam-0.9.1.ebuild

ebuild witch applies above patch if media-gfx/exiv2-0.14 is installed

------- Comment #3 From Leo 2007-05-19 09:46:43 0000 -------
Created an attachment (id=119678) [details]
ebuild_digikam_error_log

I've tried your ebuild, but it gives me the error attached :-(

------- Comment #4 From Roberto Castagnola 2007-05-19 20:58:49 0000 -------
(In reply to comment #3)
> I've tried your ebuild, but it gives me the error attached :-(

From your log, my patch isn't applied. It should be applied if
media-gfx/exiv2-0.14 is installed (which cause your error).
Try to comment condition check in my ebuild at line 65:

# if has_version ">=media-gfx/exiv2-0.14"; then
    epatch "${FILESDIR}/${P}-exiv2.patch"
# fi

------- Comment #5 From Leo 2007-05-20 11:21:20 0000 -------
(In reply to comment #4)
> (In reply to comment #3)
> > I've tried your ebuild, but it gives me the error attached :-(
> 
> From your log, my patch isn't applied. It should be applied if
> media-gfx/exiv2-0.14 is installed (which cause your error).
> Try to comment condition check in my ebuild at line 65:
> 
> # if has_version ">=media-gfx/exiv2-0.14"; then
>     epatch "${FILESDIR}/${P}-exiv2.patch"
> # fi
> 

You was right... it was emerged the wrong ebuild... I just renamed your in to
"-r2" now it works great :-)

tnx

------- Comment #6 From James Tomlinson 2007-05-21 16:29:02 0000 -------
I can confirm this patch/ebuild fixed the same problem here. Thanks.

------- Comment #7 From Wulf Krueger (RETIRED) 2007-05-21 20:17:54 0000 -------
Thanks for the patch. I've just committed the fixes to CVS.