Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

artificially bump the version number of the scipy and scipy_sandbox spkg's #8025

Closed
williamstein opened this issue Jan 21, 2010 · 4 comments
Closed

Comments

@williamstein
Copy link
Contributor

Component: build

Issue created by migration from https://trac.sagemath.org/ticket/8025

@williamstein
Copy link
Contributor Author

comment:1

Definitely "sage -upgrade" doesn't work right now (from 4.3 to 4.3.1).
Definitely doing

  sage -f spkg/standard/scipy_sandbox-20071020.p4.spkg
  sage -f spkg/standard/scipy-0.7.p3.spkg

fixes the problem. But I'm confused since scipy and scipy_sandbox depend on fortran, so they should be forced to be rebuilt anyways. Hmm..

@williamstein williamstein added this to the sage-4.3.2 milestone Jan 21, 2010
@williamstein
Copy link
Contributor Author

comment:2

More precisely, the following fixes the problem:

./sage -f numpy-1.3.0.p2.spkg scipy_sandbox-20071020.p4.spkg scipy-0.7.p3.spkg

@jhpalmieri
Copy link
Member

comment:3

Deferred to Sage 5.0 since I don't see a patch or new spkg's.

@jhpalmieri jhpalmieri modified the milestones: sage-4.4, sage-5.0, sage-4.4.1 Apr 23, 2010
@williamstein
Copy link
Contributor Author

comment:5

I've bumped both spkg version numbers, as requested, for sage-4.4.3.alpha2.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants