With version: dmapd-0.0.25-3.fc13.x86_64 # sudo /etc/init.d/dmapd start Starting dmapd: /usr/lib64/dmapd/0.0.25/modules/libphoto-meta-reader-vips.so: cannot open shared object file: No such file or directory ** ERROR **: Error opening /usr/lib64/dmapd/0.0.25/modules/libphoto-meta-reader-vips.so aborting... /bin/bash: line 1: 3619 Aborted (core dumped) /usr/sbin/dmapd
Looking in configure.ac in the package, it seems that dmapd needs at least vips 7.22: PKG_CHECK_MODULES(VIPS, vips-7.22, HAVE_VIPS=yes, HAVE_VIPS=no) but F-13 only has: vips-devel-7.20.7-3.fc13.x86_64 Hence the reason that it won't compile the plugin, however I don't understand why dmapd doesn't just ignore that feature and not attempt to use it. Either way, this needs to be fixed, either by updated vips or by patching out the call to load this library somehow, otherwise dmapd is currently unusable on F-13.
Still seeing this in Fedora 15 with dmapd-0.0.37-1.fc15.x86_64 .
This message is a reminder that Fedora 13 is nearing its end of life. Approximately 30 (thirty) days from now Fedora will stop maintaining and issuing updates for Fedora 13. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as WONTFIX if it remains open with a Fedora 'version' of '13'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version prior to Fedora 13's end of life. Bug Reporter: Thank you for reporting this issue and we are sorry that we may not be able to fix it before Fedora 13 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora please change the 'version' of this bug to the applicable version. If you are unable to change the version, please add a comment here and someone will do it for you. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete. The process we are following is described here: http://fedoraproject.org/wiki/BugZappers/HouseKeeping
As I mentioned in a comment above, this bug still occurs in Fedora 15. Could someone with permissions change the Fedora version number to 15 so the bug won't automatically close?
Fedora 13 changed to end-of-life (EOL) status on 2011-06-25. Fedora 13 is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug. If you can reproduce this bug against a currently maintained version of Fedora please feel free to reopen this bug against that version. Thank you for reporting this bug and we are sorry it could not be fixed.
As Adam mentioned, this bug affects Fedora 15 in the same way. However, downloading the source RPM with yumdownloader, installing the required devel packages, and rebuilding locally with rpmbuild results in an RPM which does include libphoto-meta-reader-vips.so.
I'm using Fedora 15 and see this problem. $ rpm -q dmapd dmapd-0.0.37-1.fc15.i686
dmapd-0.0.37-3.fc16 has been submitted as an update for Fedora 16. https://admin.fedoraproject.org/updates/dmapd-0.0.37-3.fc16
dmapd-0.0.37-3.fc15 has been submitted as an update for Fedora 15. https://admin.fedoraproject.org/updates/dmapd-0.0.37-3.fc15
Package dmapd-0.0.37-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 dmapd-0.0.37-3.fc16' as soon as you are able to. Please go to the following url: https://admin.fedoraproject.org/updates/dmapd-0.0.37-3.fc16 then log in and leave karma (feedback).
dmapd-0.0.37-3.fc16 has been pushed to the Fedora 16 stable repository. If problems still persist, please make note of it in this bug report.
dmapd-0.0.37-3.fc15 has been pushed to the Fedora 15 stable repository. If problems still persist, please make note of it in this bug report.