Description of problem: When starting weka, it prints error messages about not being able to find java_cup.* classes. This is fixed by adding set_classpath "java_cup" to /usr/bin/weka. This also seems to indicate that java_cup should be a package requirement of weka (which it doesn't seem to be) -- although it's an indirect requirement of other java-related things. Version-Release number of selected component (if applicable): weka-3.6.2-2.fc12.1.x86_64 How reproducible: Every time
Thanks for reporting, I'll fix that asap, including the possible db bindings.
weka-3.6.2-3.fc12 has been submitted as an update for Fedora 12. http://admin.fedoraproject.org/updates/weka-3.6.2-3.fc12
weka-3.6.2-3.fc13 has been submitted as an update for Fedora 13. http://admin.fedoraproject.org/updates/weka-3.6.2-3.fc13
weka-3.6.2-4.fc13 has been pushed to the Fedora 13 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 weka'. You can provide feedback for this update here: http://admin.fedoraproject.org/updates/weka-3.6.2-4.fc13
weka-3.6.2-4.fc12 has been pushed to the Fedora 12 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 weka'. You can provide feedback for this update here: http://admin.fedoraproject.org/updates/weka-3.6.2-4.fc12
Some error even with weka-3.6.2-4 ---Registering Weka Editors--- Trying to add database driver (JDBC): RmiJdbc.RJDriver - Error, not in CLASSPATH? Trying to add database driver (JDBC): jdbc.idbDriver - Error, not in CLASSPATH? Trying to add database driver (JDBC): com.mckoi.JDBCDriver - Error, not in CLASSPATH?
weka-3.6.2-4.fc12 has been pushed to the Fedora 12 stable repository. If problems still persist, please make note of it in this bug report.
weka-3.6.2-4.fc13 has been pushed to the Fedora 13 stable repository. If problems still persist, please make note of it in this bug report.