Description of problem: digiKam no longer saves the full tag path in the IPTC keyword values to improve compatability with other programs. To offset this the developers moved the full tag data into a digiKam namespace of the XMP data. Unfortunately due to a bug in libkexif this data doesn't get written into the file. Version-Release number of selected component (if applicable): How reproducible: Asign a mul Steps to Reproduce: 1. Set digiKame to save tag information in the file metadata 2. Assign a multi level tag to a image and apply the changes. Actual results: Only the last level of the tag is saved to the IPTC keywords. The full tag information isn't stored anywhere. Expected results: The full tag information should get saved to a dedicated digiKam namespace in the XMP data. Additional info: The upstream KDE bug indicates that the fix is already in libkexiv2 0.6 but the version included in kdegraphics is 0.5 for both F 10 and rawhide.
I'll double-check things in the upstream report. To be clear please, rpm -q digikam kdegraphics-libs
(In reply to comment #1) My apologies I should have done that in the initial report. $ rpm -q digikam kdegraphics-libs digikam-0.10.0-1.fc10.i386 kdegraphics-libs-4.2.2-3.fc10.i386 The same problem is also present in rawhide as well. I think the fix will require back porting a patch to libkexiv2 0.5 as 0.6 is slated for KDE 4.2.3
0.6 will be in kde-4.2.3? Cool, we'll be getting that within some weeks.
I think I may have to take that back. I went and looked at the 4.2 branch in KDE's svn and it looks like its still at 0.5.0. :-(
Looks like 4.3rc1 is still using 0.5.0 as well. -- Steven M. Parrish - KDE Triage Master - PackageKit Triager Fedora Bugzappers volunteer triage team https://fedoraproject.org/wiki/BugZappers
Naw, $ rpm -q kdegraphics-devel kdegraphics-devel-4.2.90-1.fc11.x86_64 $ pkg-config --modversion libkexiv2 0.6.0
Ping -- Steven M. Parrish - KDE Triage Master - PackageKit Triager Fedora Bugzappers volunteer triage team https://fedoraproject.org/wiki/BugZappers
Should be fixed by the KDE 4.3.0 update, please reopen if the problem persists.