#9434: Stop greping for a non-existent sage-banner
---------------------------------+------------------------------------------
Reporter: drkirkby | Owner: drkirkby
Type: defect | Status: closed
Priority: minor | Milestone: sage-4.6.1
Component: build | Resolution: fixed
Keywords: scripts VERSION.txt | Author: John Palmieri
Upstream: N/A | Reviewer: Jeroen Demeyer, David Kirkby
Merged: sage-4.6.1.alpha3 | Work_issues:
---------------------------------+------------------------------------------
Comment(by mpatel):
Replying to [comment:35 mpatel]:
> I've reported on [http://groups.google.com/group/sage-
devel/browse_thread/thread/461c1eeb61cc6f45/56108269d1090223?#56108269d1090223
sage-devel] a ''possible'' problem involving `VERSION.txt` and failed
upgrades.
Does `download_file("VERSION.txt")` attempt to download a non-existent
file, e.g.,
http://sage.math.washington.edu/home/release/sage-4.6.1.alpha3/sage-4.6.1.alpha3/spkg/VERSION.txt
? The successful upgrades I've done from 4.6 to 4.6.1.alpha3 somehow
avoid this problem --- after the upgrade, `SAGE_ROOT` does not contain a
`VERSION.txt`. But upgrades that failed I cannot resume:
{{{
$ ./sage -upgrade
http://sage.math.washington.edu/home/release/sage-4.6.1.alpha3/sage-4.6.1.alpha3
[...]
http://sage.math.washington.edu/home/release/sage-4.6.1.alpha3/sage-4.6.1.alpha3/spkg/VERSION.txt
--> VERSION.txt [.]
Failed to download
'http://sage.math.washington.edu/home/release/sage-4.6.1.alpha3/sage-4.6.1.alpha3/spkg/VERSION.txt'.
Abort.
$
}}}
--
Ticket URL: <http://trac.sagemath.org/sage_trac/ticket/9434#comment:36>
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.
