#9583: Unhandled SIGSEGV with 4.5.2.alpha0 on t2
-----------------------+----------------------------------------------------
Reporter: mpatel | Owner: drkirkby
Type: defect | Status: needs_review
Priority: blocker | Milestone: sage-4.5.2
Component: solaris | Keywords:
Author: | Upstream: N/A
Reviewer: | Merged:
Work_issues: |
-----------------------+----------------------------------------------------
Comment(by drkirkby):
Would Mitesh, (who is a release manager for 4.3.2), consider merging the
package at #8059, despite it being a major update to Singular, if it fixes
this problem? I know the plan was not to update .spkg files in Sage 4.3.2,
but plans do sometimes change.
If my understanding is correct,
http://sage.math.washington.edu/home/malb/spkgs/singular-3-1-1-4.spkg
which is the latest release, does not define Kstd1_mu to be mu, so this
particular problem should not exist. However, since
{{{singular-3-1-1-4.spkg}}} has not been checked properly on 't2', there
may be other problems.
It seems to me that the policy the release managers adopt regarding the
updating of .spkg files could have a major impact on what happens on this
ticket.
Dave
--
Ticket URL: <http://trac.sagemath.org/sage_trac/ticket/9583#comment:45>
Sage <http://www.sagemath.org>
Sage: Creating a Viable Open Source Alternative to Magma, Maple, Mathematica,
and MATLAB
--
You received this message because you are subscribed to the Google Groups
"sage-trac" group.
To post to this group, send email to [email protected].
To unsubscribe from this group, send email to
[email protected].
For more options, visit this group at
http://groups.google.com/group/sage-trac?hl=en.
