You need to run "make" to install the updated scripts in local/, did you do that?
On Wednesday, December 25, 2013 4:21:51 PM UTC, P Purkayastha wrote: > > 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. > > On 12/26/2013 12:12 AM, Volker Braun wrote: > > 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. > > > > followed by > > .../src/sage/sage-6.0.server> ./sage -upgrade develop > > > > > > -- > > 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 [email protected] <javascript:>. > > For more options, visit https://groups.google.com/groups/opt_out. > > -- 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 [email protected]. For more options, visit https://groups.google.com/groups/opt_out.
