Arch Linux

Please read this before reporting a bug:
https://wiki.archlinux.org/title/Bug_reporting_guidelines

Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.

REPEAT: Do NOT report bugs for outdated packages!
Tasklist

FS#13867 - missing dependency in kdegraphics

Attached to Project: Arch Linux
Opened by Martin Stolpe (BertiBoeller) - Thursday, 19 March 2009, 11:26 GMT
Last edited by Pierre Schmitz (Pierre) - Friday, 20 March 2009, 10:59 GMT
Task Type Bug Report
Category Packages: Extra
Status Closed
Assigned To No-one
Architecture All
Severity Low
Priority Normal
Reported Version
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 0
Private No

Details

Description: exiv2 is missing as a dependency in the kdegraphics package
This task depends upon

Closed by  Pierre Schmitz (Pierre)
Friday, 20 March 2009, 10:59 GMT
Reason for closing:  Not a bug
Comment by Pierre Schmitz (Pierre) - Thursday, 19 March 2009, 12:38 GMT
I am not sure if I get this right. A dep entry is not needed because it depends indirectly on exiv2:

exiv2 -> strigi -> kdelibs -> kdegraphics
Comment by Martin Stolpe (BertiBoeller) - Thursday, 19 March 2009, 14:04 GMT
Hi,
I'm not very familiar with dependecies. There are two reasons why I made this bug report:

1. namcap lists exiv2 as a dependency

2. I have exiv2 version 0.18 installed on my system. When I tried to use digikam 0.10.0 it didn't work. Then I tried to compile digikam from source and got an error which was related to exiv2. After I compiled kdegraphics from source against my installed exiv2, digkam compiled perfectly.
Comment by Jan de Groot (JGC) - Thursday, 19 March 2009, 14:31 GMT
I don't know for sure, but could it be that exiv2 received a soname bump when upgrading to 0.18 on your system? The official packaged version is still 0.17.
Comment by Martin Stolpe (BertiBoeller) - Thursday, 19 March 2009, 15:06 GMT
I don't understand what you mean by "soname bump" but here's what I did:

Yes the official version is still 0.17. I tried to build a PKBUILD for digikam 0.10.0 (before it was released on extra). The README from libkexiv2 (svn://anonsvn.kde.org/home/kde/branches/KDE/4.2/kdegraphics/libs/libkexiv2) does recommend version 0.18 for exiv2, so I compiled and installed version 0.18 on my system. That's the reason why I have 0.18 installed on my system.

Anyway I still want to know if exiv2 is a dependency for kdegraphics or not. ;-)
Comment by Gerardo Exequiel Pozzi (djgera) - Thursday, 19 March 2009, 18:07 GMT
Is correct

libgwenviewlib.so.4.2.0 and libkexiv2.so.7.2.0 from kdegraphics-4.2.1-1-i686 depends on libexiv2.so.4
Comment by Pierre Schmitz (Pierre) - Friday, 20 March 2009, 10:01 GMT
I am not sure what to do with this bug report now. There is no problem with the packages from extra, right? Your problem is that you have compiled exiv2 0.18 which is not compatible to 0.17 from extra. (There is an API and file name chagne; that's what Jan meant with so name bump)
Comment by Martin Stolpe (BertiBoeller) - Friday, 20 March 2009, 10:17 GMT
Hm, perhaps include exiv2 as a dependency in the next version of the kdegraphics package (I think 4.2.2 shouldn't be too far away). As far as I understand dependencies everything which is needed to run the program should be included as a dependency in the package and kdegraphics seems to need exiv2.
Comment by Jan de Groot (JGC) - Friday, 20 March 2009, 10:20 GMT
It's included in the dependency chain by strigi, which is a dependency for kdelibs. When you bump random packages on your system to versions which are incompatible with the official ones, you'll break library linking. This is what you see on your system at this moment.
Comment by Martin Stolpe (BertiBoeller) - Friday, 20 March 2009, 10:46 GMT
Hm, ok I think I've learned some things about dependencies. I'm sorry that you had to suffer for my learning experience. ;-)

Requested to close that "bug".

Loading...