Description of problem: strigidaemon is not able to start. The error message is: Unknown backend type: clucene Also "strigidaemon --backends" don't list any backends. Version-Release number of selected component (if applicable): strigi-0.5.7-1.fc8.x86_64 strigi-libs-0.5.7-1.fc8.x86_64 clucene-core-0.9.20-2.fc8.x86_64 How reproducible: ever Steps to Reproduce: 1. start "strigidaemon" from a terminal Actual results: no starting Expected results: should start Additional info: build log of actual version has not really found clucene: -- Found CLucene library: /usr/lib64/libclucene.so -- Found CLucene include dir: /usr/include Could not find CLucene. Please install CLucene = 0.9.16a (http://clucene.sf.net) http://koji.fedoraproject.org/packages/strigi/0.5.7/1.fc8/data/logs/x86_64/build.log But also a local rebuilt without this error stops with the same error message.
strigi-0.5.7-2.fc8 has been submitted as an update for Fedora 8
strigi-0.5.7-2.fc7 has been submitted as an update for Fedora 7
As I've said, a simple rebuilt don't fix the main problem. Only the build error is gone.
The build error sounds like badly broken too though. But why is it still not finding the backend? Multilib issue maybe?
(In reply to comment #3) > As I've said, a simple rebuilt don't fix the main problem. Only the build > error is gone. O.K, maybe I don't understand you at first, however this rebuild is necessary too.
strigi-0.5.7-2.fc7 has been pushed to the Fedora 7 testing repository. If problems still persist, please make note of it in this bug report. If you want to test the update, you can install it with su -c 'yum --enablerepo=updates-testing update strigi'. You can provide feedback for this update here: http://admin.fedoraproject.org/updates/F7/FEDORA-2008-1874
(In reply to comment #4) > The build error sounds like badly broken too though. > But why is it still not finding the backend? Multilib issue maybe? Just tried it in i386. Same problem.
Upstream released 0.5.8 2 days ago, maybe that fixes it. Should I try submitting builds for that?
(In reply to comment #8) > Upstream released 0.5.8 2 days ago, maybe that fixes it. Should I try > submitting builds for that? I've rebuilt strigi-0.8.2 locally and the problem still occurs (only tested i386). clucene-core-0.9.20-2.fc8 strigi-0.5.8-1.fc8 strigi-libs-0.5.8-1.fc8
I see the problem: This is due to an error in the hand-coded cmake invocation: -DLIB_DESTINATION=lib%{lib_suffix} LIB_DESTINATION should be an absolute path, i.e.: -DLIB_DESTINATION=%{_libdir}
Can you please try this build? http://koji.fedoraproject.org/koji/buildinfo?buildID=38754
Confirmed to work on i386 and x86_64. Thanks!
strigi-0.5.8-1.fc8 has been submitted as an update for Fedora 8
strigi-0.5.8-1.fc7 has been submitted as an update for Fedora 7
strigi-0.5.8-1.fc7 has been pushed to the Fedora 7 stable repository. If problems still persist, please make note of it in this bug report.
strigi-0.5.8-1.fc8 has been pushed to the Fedora 8 stable repository. If problems still persist, please make note of it in this bug report.