Bug 207063

Summary: maxima-runtime-sbcl and sbcl out of sync
Product: [Fedora] Fedora Reporter: Leo <sdl.web>
Component: maximaAssignee: Rex Dieter <rdieter>
Status: CLOSED NEXTRELEASE QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: medium Docs Contact:
Priority: medium    
Version: 5CC: extras-qa
Target Milestone: ---   
Target Release: ---   
Hardware: All   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2006-10-31 21:13:04 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:

Description Leo 2006-09-19 01:56:55 UTC
Description of problem:
maxima-runtime-sbcl is not dependent on specific version of sbcl making it
possible to get a broken maxima. For example, sbcl 0.9.16 has been in extras for
a few weeks and maxima-runtime-sbcl is built for sbcl 0.9.14 and thus users get
an error:

shell-init: error retrieving current directory: getcwd: cannot access parent
directories: No such file or directory
fatal error encountered in SBCL pid 13645(tid 3085321920):
can't load .core for different runtime, sorry

LDB monitor
ldb> 

Version-Release number of selected component (if applicable):


How reproducible:


Steps to Reproduce:
1.
2.
3.
  
Actual results:


Expected results:


Additional info:

Comment 1 Rex Dieter 2006-10-31 21:13:04 UTC
My apologies, this has been fixed for quite awhile now, I just forgot to mention
that here.  Thanks for the report.