#9434: Stop greping for a non-existent sage-banner
---------------------------------+------------------------------------------
Reporter: drkirkby | Owner: drkirkby
Type: defect | Status: new
Priority: blocker | Milestone: sage-4.6.1
Component: build | Resolution:
Keywords: scripts VERSION.txt | Author: John Palmieri
Upstream: N/A | Reviewer: Jeroen Demeyer, David Kirkby
Merged: sage-4.6.1.alpha3 | Work_issues: Fix download of VERSION.txt
---------------------------------+------------------------------------------
Comment(by mpatel):
Using `download_file("../VERSION.txt")` may also work (I've tested this
only once).
For me, the upgrades that failed were parallel spkg builds. But some
parallel spkg upgrades did "succeed," i.e., modulo SageNB not being
upgraded. (Were there any other packages not upgraded?)
All purely serial and parallel-only-within-spkg upgrades "succeeded."
Could when the new `sage_scripts` package is installed matter for either
the `VERSION.txt` discrepancy or the apparently separate SageNB problem?
--
Ticket URL: <http://trac.sagemath.org/sage_trac/ticket/9434#comment:40>
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.
