#8236: installing spkg from remote location must leave a spkg (placeholder) in
spkg/
------------------------------+---------------------------------------------
Reporter: dimpase | Owner: GeorgSWeber
Type: defect | Status: new
Priority: major | Milestone:
Component: build | Keywords: spkg, installation
Author: Dima Pasechnik | Upstream: N/A
Reviewer: | Merged:
Work_issues: |
------------------------------+---------------------------------------------
When one does sage -f (or -i) from a remote location, the
spkg file is not stored locally in the appropriate place,
even if an upgrade of a standard spkg has taken place.
As a result, the script spkg/standard/newest_version may fail
to detect that the upgrade has taken place.
As a solution, one can either store the full downloaded spkg, or
just a placeholder with (almost) the same name as the spkg file.
Or, perhaps, sage -i (-f) can call spkg/standard/newest_version to see if
an upgrade is happening, and act accordingly.
This bug has cost me and wdj hours of wasted time, see #8229.
--
Ticket URL: <http://trac.sagemath.org/sage_trac/ticket/8236>
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.
