sage -upgrade idiosyncracies

[P Purkayastha]

I had set up sage-git in two ways. The first one was by following the
quickstartguide [1]. The second way was by using the sage-6.0 tarball.

First method (Quickstartguide):
-------------------------------

Now, with the first method, it seems impossible to run sage -upgrade and
have it behave properly. Here is an example output:

~/Installations/sage» ./sage -upgrade develop
fatal: 'develop' does not appear to be a git repository
fatal: Could not read from remote repository.

Please make sure you have the correct access rights
and the repository exists.
There was a failure downloading Sage's sources. Please make sure you are
connected to the internet. Aborting...
~/Installations/sage [1] »


This error is present even though the develop branch is present in the
remote repository:

~/Installations/sage [1] » git branch -r | grep origin
origin/HEAD -> origin/master
origin/develop
origin/master
origin/upstream

The following command partially works:

~/Installations/sage» ./sage -upgrade g...@trac.sagemath.org:sage.git develop
From trac.sagemath.org:sage
* [new branch] develop -> zKYBy6_CBUB4D3fkr1eEgEY5-lmwod6sahiGr0V8
Already up-to-date.
Deleted branch zKYBy6_CBUB4D3fkr1eEgEY5-lmwod6sahiGr0V8 (was 036984d).
/mnt/usb/Installations/sage/local/bin/sage-upgrade: line 59:
sage-real-upgrade: command not found

Followed this by a "make" and it recompiled maxima, and other than that
I do not see any other changes.

Second method (sage-6.0 tarball):
---------------------------------

With the second method it is all very smooth. I did a

.../src/sage/sage-6.0.server> git fetch origin

followed by

.../src/sage/sage-6.0.server> ./sage -upgrade develop



The main problem:
-----------------

After a bit more investigating, it turns out that most of the scripts in
SAGE_ROOT/local/bin are all at some old version from Dec 14. A bunch of
questions:

1. So, even though I started out with sage-git from pre-6.0 version, at
some point sage itself got upgraded but not installed (at least the
scripts)?

2. How can I (manually) install the new scripts? Should I just copy the
files from src/bin?

3. How can I prevent this problem from recurring in the future?


[1] http://trac.sagemath.org/wiki/QuickStartSageGit

[Volker Braun]

It seems your first installation is pre-6.0. Before that was released there were bugs in the upgrade script. Use git to manually upgrade to 6.0 first, then "sage -upgrade" will (should) work.

On Wednesday, December 25, 2013 2:22:43 PM UTC, P Purkayastha wrote:

With the second method it is all very smooth. I did a
.../src/sage/sage-6.0.server> git fetch origin

The fetch is also performed by the upgrade script, no need to do it manually.

[P Purkayastha]

Well, that's the problem. local/bin is not tracked by git. And I am not
sure how else I can force the upgrade of the scripts. In terms of the
sage library, I am already on sage-6.1.beta2.

> --
> You received this message because you are subscribed to the Google
> Groups "sage-git" group.
> To unsubscribe from this group and stop receiving emails from it, send
> an email to sage-git+u...@googlegroups.com.
> For more options, visit https://groups.google.com/groups/opt_out.

[Volker Braun]

You need to run "make" to install the updated scripts in local/, did you do that?

[P Purkayastha]

Yes.

The output of make (run again; nothing to update) is attached. There are
no differences between github, trac and my local develop branch.

~/Installations/sage» git rev-parse --abbrev-ref HEAD
develop
~/Installations/sage» git diff develop origin/develop
~/Installations/sage» diff -q local/bin/sage-upgrade src/bin/sage-upgrade
Files local/bin/sage-upgrade and src/bin/sage-upgrade differ
~/Installations/sage [1] » git diff develop trac/develop
~/Installations/sage»

> > an email to sage-git+u...@googlegroups.com <javascript:>.

> > For more options, visit https://groups.google.com/groups/opt_out

> <https://groups.google.com/groups/opt_out>.

[Volker Braun]

Do a "make distclean" to rebuild from scratch. I'm pretty sure that the post-6.0 scripts will copy updates to local as required. Let us know if you see this behavior again...