Description of problem: There is a bug in exiv2 0.21.1 that can cause it and the application using it (in my case gthumb) to crash. See http://dev.exiv2.org/issues/769 for details. According to this site, the bug has been fixed in version 0.22. Version-Release number of selected component (if applicable): 0.21.1-1 If at all possible, please release an updated package for F15. Thanks.
exiv2-0.22 is api/abi incompatible with 0.21.1, but I could see of the fix can be backported.
Oh yeah, seems so, http://dev.exiv2.org/projects/exiv2/repository/revisions/2562 http://dev.exiv2.org/projects/exiv2/repository/revisions/2562/diff?format=diff&rev_to=2561
mind testing this out? http://koji.fedoraproject.org/koji/taskinfo?taskID=3379664
exiv2-0.21.1-3.fc14 has been submitted as an update for Fedora 14. https://admin.fedoraproject.org/updates/exiv2-0.21.1-3.fc14
exiv2-0.21.1-3.fc15 has been submitted as an update for Fedora 15. https://admin.fedoraproject.org/updates/exiv2-0.21.1-3.fc15
exiv2-0.21.1-3.fc16 has been submitted as an update for Fedora 16. https://admin.fedoraproject.org/updates/exiv2-0.21.1-3.fc16
Package exiv2-0.21.1-3.fc16: * should fix your issue, * was pushed to the Fedora 16 testing repository, * should be available at your local mirror within two days. Update it with: # su -c 'yum update --enablerepo=updates-testing exiv2-0.21.1-3.fc16' as soon as you are able to. Please go to the following url: https://admin.fedoraproject.org/updates/exiv2-0.21.1-3.fc16 then log in and leave karma (feedback).
I have tested exiv2-0.21.1-3.fc15 from Comment 5 and it works perfectly. Thank you very much for your ultra-fast help on this!
exiv2-0.21.1-3.fc16 has been pushed to the Fedora 16 stable repository. If problems still persist, please make note of it in this bug report.
exiv2-0.21.1-3.fc14 has been pushed to the Fedora 14 stable repository. If problems still persist, please make note of it in this bug report.
exiv2-0.21.1-3.fc15 has been pushed to the Fedora 15 stable repository. If problems still persist, please make note of it in this bug report.