On Mon, Apr 25, 2011 at 2:19 PM, Jason Grout
wrote:
> On 4/25/11 6:10 AM, John Cremona wrote:
>>
>> Thanks for the various comments.
>>
>> I have definitely used cp to copy sage from one place to another
>> before, with expected behaviour on first startup. This time I used
>> scp for some reason.
On 4/25/11 6:10 AM, John Cremona wrote:
Thanks for the various comments.
I have definitely used cp to copy sage from one place to another
before, with expected behaviour on first startup. This time I used
scp for some reason. I just redid it using rsync, following Dave's
suggestion, and everyt
Thanks for the various comments.
I have definitely used cp to copy sage from one place to another
before, with expected behaviour on first startup. This time I used
scp for some reason. I just redid it using rsync, following Dave's
suggestion, and everything is normal.
John
On Mon, Apr 25, 201
On 04/25/11 08:46 AM, Dima Pasechnik wrote:
On Apr 25, 3:39 am, John Cremona wrote:
I just moved a fresh build in this way (using scp -pr, though source
and destination were local) and the first time I run Sage from the new
location is starts up normally.
John
Using rsync will be a
> > I just moved a fresh build in this way (using scp -pr, though source
> > and destination were local) and the first time I run Sage from the new
> > location is starts up normally.
>
> I can't reproduce this.
> Have you actually moved anything?
I ran into something like this once too. I can't
On Apr 25, 3:39 am, John Cremona wrote:
> It always used to be the case that if you moved the entire Sage build
> tree to another place, the first time you ran Sage from the new place
> it issued a warning to wait a while while it updated some hard-wired
> paths, Has anything changed to make th
