Description of problem: I just installed maxima-runtime-cmucl-5.21.1-3.fc14.i686, launched it, to get the error message: /usr/lib/cmucl/bin/lisp: no such file By default, maxima depends upon maxima-runtime-cmucl-5.21.1-3.fc14.i686 But I had to install cmucl manually to get this runtime working. It is possible to add a depency of cmucl (cmucl-20a-1.fc13.i686) into maxima-runtime-cmucl-5.21.1-3.fc14.i686 ? Version-Release number of selected component (if applicable): How reproducible: Steps to Reproduce: 1. yum -y install maxima 2. 3. Regards Pascal Dupuis
you probably want to use maxima-runtime-sbcl anyway (which should be the default. the -cmucl backend seems to have some problems, and will likely be dropped in the near future.
Strange. A 'yum deplist maxima' lists indeed 'maxima-runtime-sbcl' as first dependency, yet when I installed 'maxima', yum picked maxima-runtime-cmucl as run-time engine. Regards Pascal
Yeah, I think it's an interesting quirk of yum's depsolving, that -runtime-cmucl has less dependencies to pull in, so *sometimes* gets preferred. Newer builds will now have a hard dependency on the default runtime (sbcl).
OK. Thank you. Feel free to close it.
maxima-5.22.1-5.fc13 has been submitted as an update for Fedora 13. https://admin.fedoraproject.org/updates/maxima-5.22.1-5.fc13
maxima-5.22.1-5.fc14 has been submitted as an update for Fedora 14. https://admin.fedoraproject.org/updates/maxima-5.22.1-5.fc14
maxima-5.22.1-5.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 maxima'. You can provide feedback for this update here: https://admin.fedoraproject.org/updates/maxima-5.22.1-5.fc13
maxima-5.22.1-5.fc14 has been pushed to the Fedora 14 stable repository. If problems still persist, please make note of it in this bug report.
maxima-5.22.1-5.fc13 has been pushed to the Fedora 13 stable repository. If problems still persist, please make note of it in this bug report.