Description of problem:
Weka's LibSVM component doesn't work as other classifiers and returns the:
"libsvm classes not in CLASSPATH!" error.
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1. Start Weka Explorer
2. Load some data
3. Select Classify tab and choose the LibSVM classifier
4. Press Start
Weka produces the following error:
Command: weka.classifiers.functions.LibSVM -S 0 -K 2 -D 3 -G 0.0 -R 0.0 -N 0.5 -M 40.0 -C 1.0 -E 0.001 -P 0.1
libsvm classes not in CLASSPATH!
Just one more note, I have the following LibSVM packages installed:
There are actually three problems:
1) weka doesn't Requires: libsvm-java
2) if installed, libsvm-java is not in the classpath
Adding the following line to /usr/bin/weka:
set_classpath "libsvm.jar" (before run "")
would be enough if libsvm.jar would be placed correctly in /usr/share/java.
3) as this is not the case, you should now modify /usr/bin/weka in the following way:
I've filed bug 524108 and would like to fix this and release updates after that one is resolved together with updating to 3.6.1.
Thanks for reporting!
Thanks for your quick response!
Just a "ping" on how should we proceed with this issue.
Since libsvm-java-2.89-4.fc10.i386, libsvm.jar is now correctly placed in /usr/share/java.
Should weka now require libsvm-java and should we fix /usr/bin/weka according to 2) from your previous comment?
As is now, weka still doesn't work with LibSVM out of the box.
This message is a reminder that Fedora 10 is nearing its end of life.
Approximately 30 (thirty) days from now Fedora will stop maintaining
and issuing updates for Fedora 10. 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 '10'.
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 10'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 10 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:
Another "ping", same as in comment #4 is still true for F12.
weka-3.6.2-1.fc12 has been submitted as an update for Fedora 12.
Ok, thank you for working on fixing this bug.
I still have another request:
Weka package should require libsvm-java as you said in comment #2.
I think this is the last piece missing to seamless SVM support in Weka.
Of course, I'm totally dumb -- sorry! New builds are already going on...
weka-3.6.2-2.fc13 has been submitted as an update for Fedora 13.
weka-3.6.2-2.fc12 has been submitted as an update for Fedora 12.
weka-3.6.2-2.fc13 has been pushed to the Fedora 13 stable repository. If problems still persist, please make note of it in this bug report.
weka-3.6.2-2.fc12.1 has been submitted as an update for Fedora 12.
weka-3.6.2-2.fc12.1 has been pushed to the Fedora 12 stable repository. If problems still persist, please make note of it in this bug report.