#9583: Unhandled SIGSEGV with 4.5.2.alpha0 on t2
----------------------------+-----------------------------------------------
Reporter: mpatel | Owner: drkirkby
Type: defect | Status: positive_review
Priority: blocker | Milestone: sage-4.5.2
Component: solaris | Keywords:
Author: Dan Drake | Upstream: N/A
Reviewer: Mitesh Patel | Merged:
Work_issues: |
----------------------------+-----------------------------------------------
Comment(by mpatel):
Replying to [comment:50 jhpalmieri]:
> As I said, after upgrading, you have to make sure to do "sage -ba". Is
this automatic in the upgrade process?
As far as I can tell, `sage -upgrade` (which invoke `sage-upgrade` and
`sage-update`) and `sage -f/i` (which call `sage-spkg`) do not check
whether it's necessary to rebuild dependent packages (nor warn about or
actually rebuild them), particularly those that are already installed
(i.e., have a corresponding marker in `SAGE_ROOT/spkg/installed`). Or am
I misunderstanding your question?
--
Ticket URL: <http://trac.sagemath.org/sage_trac/ticket/9583#comment:58>
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.
