Opened 12 years ago

Closed 8 years ago

#8236 closed defect (wontfix)

installing spkg from remote location must leave a spkg (placeholder) in spkg/

Reported by: dimpase Owned by: GeorgSWeber
Priority: major Milestone: sage-duplicate/invalid/wontfix
Component: build Keywords: spkg, installation
Cc: Merged in:
Authors: Reviewers: Dima Pasechnik, Jeroen Demeyer
Report Upstream: N/A Work issues:
Branch: Commit:
Dependencies: Stopgaps:

Status badges


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.

Change History (5)

comment:1 Changed 12 years ago by dimpase

  • Status changed from new to needs_info

This issue was discussed here:

in a nutshell, newest_version should not be used for these tasks, and a new script has to be written.

comment:2 Changed 8 years ago by jdemeyer

  • Milestone set to sage-duplicate/invalid/wontfix
  • Reviewers set to Jeroen Demeyer
  • Status changed from needs_info to needs_review

It's not exactly clear what this bug is about, but given the many changes to sage-spkg, it's a good bet to assume that it's fixed.

comment:3 Changed 8 years ago by jdemeyer

  • Status changed from needs_review to positive_review

comment:4 Changed 8 years ago by jdemeyer

  • Authors Dima Pasechnik deleted
  • Reviewers changed from Jeroen Demeyer to Dima Pasechnik, Jeroen Demeyer

comment:5 Changed 8 years ago by vbraun

  • Resolution set to wontfix
  • Status changed from positive_review to closed
Note: See TracTickets for help on using tickets.