In gmane.comp.mathematics.sage.support, you wrote:
> My fault. I should have written "My .bashrc file aliases cp to 'cp
> -i' and mv to 'mv -i'".
>
> Strangely, unaliasing those commands did not stop the problem. I
> still had to type in "y" a bunch of times after I tried the command
> "sage -i n
On Monday, April 3, 2017 at 1:28:31 PM UTC-4, Volker Braun wrote:
>
> I don't think that old version of Sage runs on sierra, you need to get a
> more recent latest version.
>
Yeah, I agree that a Sage binary built for 10.6 has not much chance of
running on 10.12. There should be some errors i
I don't think that old version of Sage runs on sierra, you need to get a
more recent latest version.
On Monday, April 3, 2017 at 12:53:36 AM UTC+2, Ken Smith wrote:
>
> Hi,
>
> I have been running Sage 4.7.2-OSX-64bit-10.6 on a Mac under OS El Capitan
> and it has been great. When I run the S
I doubt that this has anything to do with sage and, instead, apple broke
something in their update and you need to re-enable your local webserver.
As a first step try
sudo apachectl configtest
and see what error messages this gives. Hopefully this will tell you what
to fix. Failing that, try h
Thanks. It is done in 10 minutes.
But still feel strange that what's going on with the upgrade() function,
though I am not the one who has to worry about it.
Dima Pasechnik於 2015年3月23日星期一 UTC+1上午9時39分59秒寫道：
>
> well, for the purposes of getting up and running, you might rather prefer
> to compil
well, for the purposes of getting up and running, you might rather prefer
to compile 6.5 from source.
On Monday, 23 March 2015 06:42:39 UTC, chi...@gmail.com wrote:
>
> I am trying upgrade sage 6.4.1 to 6.5. My machine is Linux mint 17.1.
>
> When it arrives the point:
>
> ;;; About to load c
I find "hg st -ma" most useful, it shows only (m)odified and (a)added
files. And using hgignore too, to ignore things like backup files.
Maybe -ma is what this script needs?
John Cremona
On Dec 15, 6:15 pm, William Stein wrote:
> On Thu, Dec 15, 2011 at 1:59 PM, Jeroen Demeyer
> wrote:
> > On
On Dec 15, 9:45 pm, William Stein wrote:
> On Thu, Dec 15, 2011 at 7:16 AM, Anthony Wickstead
>
> wrote:
> > I am trying to upgrade my Sage 4.7.1 installation using "./sage -
> > upgrade" [and also using "upgrade()" from within sage]. After checking
> > mirrors, telling me that six packages wil
On Oct 20, 2:01 pm, Simon King <[EMAIL PROTECTED]> wrote:
> Dear Michael,
>
> On Oct 20, 7:05 pm, Simon King <[EMAIL PROTECTED]> wrote:
>
> > I think it'll be better to try from scratch (i.e., from sources).
>
> ... and that worked.
As long as you copy libstc++.so into $SAGE_LOCAL/lib Sage will
Dear Michael,
On Oct 20, 7:05 pm, Simon King <[EMAIL PROTECTED]> wrote:
> I think it'll be better to try from scratch (i.e., from sources).
... and that worked.
However, is it normal that the attempt to upgrade did *not* result in
an install.log?
Yours
Simon
--~--~-~--~~-
Hi Michael,
On Oct 20, 6:09 pm, mabshoff <[EMAIL PROTECTED]
dortmund.de> wrote:
> This looks like a problem with your toolchain since we don't ship any
> libstdc++.so since it is provided by the C++ compiler.
Ok. I have two versions of gcc on my machine, but the problem occurs
in both cases.
I
On Oct 20, 9:01 am, Simon King <[EMAIL PROTECTED]> wrote:
> Dear Team,
>
> after William's recent post that an upgrade to 3.1.4 should now be
> possible.
>
> I tried, but it failed.
>
> Strange: There was no new install.log (AFAIK, an upgrade should
> produce a new one).
>
> "Last words" on the
Hello,
> Okay, here's another big problem that seems to have come with version
> 3.1.1:
> "Edit a copy" doesn't work any more on published worksheets! Sage
> makes a copy, but I can't edit it. This is a big problem, as we're
> working with several users.
I fixed this a few days ago, and it will
Okay, here's another big problem that seems to have come with version
3.1.1:
"Edit a copy" doesn't work any more on published worksheets! Sage
makes a copy, but I can't edit it. This is a big problem, as we're
working with several users.
Please help! Thanks.
Maike
--~--~-~--~~
Robert Bradshaw wrote:
>
>>> 3. Syntax on arrows has changed. Before I gave the starting and
>>> ending
>>> point of the arrow, now you have to give the starting point and the
>>> difference between the starting and ending points (something like
>>> (3,4) meaning 3 to the right, 4 up). However
On Sep 4, 2008, at 6:37 AM, William Stein wrote:
>
> On Thu, Sep 4, 2008 at 3:53 AM, Maike
> <[EMAIL PROTECTED]> wrote:
>>
>> Hello,
>>
>> I just upgraded from 3.0.5 to version 3.1.1 and several things aren't
>> working any more:
>>
>> 1. sliders aren't showing when used with the interact-func
On Thu, Sep 4, 2008 at 3:53 AM, Maike <[EMAIL PROTECTED]> wrote:
>
> Hello,
>
> I just upgraded from 3.0.5 to version 3.1.1 and several things aren't
> working any more:
>
> 1. sliders aren't showing when used with the interact-functionality.
> It doesn't work the way it used to in the older versi
On Sun, Aug 24, 2008 at 3:20 PM, Bin Zhang <[EMAIL PROTECTED]> wrote:
>
> William Stein wrote:
>> Try
>>
>> sage: hg_scripts.pull()
>> sage: hg_scripts.merge()
>> and possibly
>> sage: hg_scripts.updae()
>>
>>
>
> sage: hg_scripts.merge()
> cd "/home/zhang/src/sage-3.1.1/local/bin" && hg mer
William Stein wrote:
> On Sun, Aug 24, 2008 at 3:20 PM, Bin Zhang <[EMAIL PROTECTED]> wrote:
>
>> William Stein wrote:
>>
>>> Try
>>>
>>> sage: hg_scripts.pull()
>>> sage: hg_scripts.merge()
>>> and possibly
>>> sage: hg_scripts.updae()
>>>
>>>
>>>
>> sage: hg_scripts.merge()
William Stein wrote:
> Try
>
> sage: hg_scripts.pull()
> sage: hg_scripts.merge()
> and possibly
> sage: hg_scripts.updae()
>
>
sage: hg_scripts.merge()
cd "/home/zhang/src/sage-3.1.1/local/bin" && hg merge
abort: repo has 3 heads - please merge with an explicit rev
sage: hg_scripts.upd
Try
sage: hg_scripts.pull()
sage: hg_scripts.merge()
and possibly
sage: hg_scripts.updae()
then restart sage.
On Sun, Aug 24, 2008 at 2:42 AM, Bin Zhang <[EMAIL PROTECTED]> wrote:
>
> Hi,
>
> I have upgraded my sage 3.0.6 to 3.1.1 using "sage -upgrade".
> It seems to me it did not upgrade
On Wed, May 28, 2008 at 5:48 PM, Hobus <[EMAIL PROTECTED]> wrote:
>
> Hi, how can i upgrade to Sage 3.0.2? i have Ubuntu 8.04
You can try typing
sage -upgrade
Assuming you have these standard ubuntu packages installed it is
very likely to work.
g++, make, m4, ranlib
Alternatively, just do
Hi, how can i upgrade to Sage 3.0.2? i have Ubuntu 8.04
Thak you
--~--~-~--~~~---~--~~
To post to this group, send email to sage-support@googlegroups.com
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more options, visit this group at
http://
On Wed, May 28, 2008 at 5:31 PM, Hobus <[EMAIL PROTECTED]> wrote:
>
> How can I upgrade, my Sage to SAGE 3.0.2 ?
Which operating system are you using? Which version of Sage are you using?
William
--~--~-~--~~~---~--~~
To post to this group, send email to sage-su
Also, you can write at the prompt:
version()
regards.
On 18 feb, 04:10, mabshoff <[EMAIL PROTECTED]
dortmund.de> wrote:
> [EMAIL PROTECTED] wrote:
> > Hi,
>
> > I have installed sage 2.9. I ran "sage -upgrade" on tuesday,
> > february the 12. Do I now have the current version, 2.10.1 (dated f
[EMAIL PROTECTED] wrote:
> Hi,
>
> I have installed sage 2.9. I ran "sage -upgrade" on tuesday,
> february the 12. Do I now have the current version, 2.10.1 (dated from
> february the 02)?
Unless the upgrade failed somehow the banner now should say
---
Dear Michael,
On Jan 6, 11:34 pm, mabshoff <[EMAIL PROTECTED]
dortmund.de> wrote:
> you might have had bad timing and updated just as William released
> 2.9.3. So try deleteing the old doc-2.9.3.spkg and run -upgrade again.
> If that fails again please post the md5sum of the doc-2.9.3.spkg you
>
On Jan 6, 11:21 pm, Simon King <[EMAIL PROTECTED]> wrote:
> Dear Sage-Support team,
>
> when i did sage -upgrade, it finished with the following error:
>
> Finished extraction
> There is no spkg-install script, no setup.py, and no configure script,
> so I do not know how to install /usr/local/sa
On Dec 4, 2007, at 07:24 , William Stein wrote:
>
> On Dec 4, 2007 6:00 AM, mabshoff
> <[EMAIL PROTECTED]> wrote:
>>
>>
>>
>> On Dec 4, 11:44 am, fwc <[EMAIL PROTECTED]> wrote:
>
>
>>
>>> I'm still not sure how to recover my old worksheets. Should I be
>>> looking elsewhere?
>>>
>>> --
>>>
On Dec 4, 2007 6:00 AM, mabshoff
<[EMAIL PROTECTED]> wrote:
>
>
>
> On Dec 4, 11:44 am, fwc <[EMAIL PROTECTED]> wrote:
>
> > I'm still not sure how to recover my old worksheets. Should I be
> > looking elsewhere?
> >
> > --
> >
> > If the files are now going to be in ~/.sage/sage_notebook
On Dec 4, 2007 6:00 AM, mabshoff
<[EMAIL PROTECTED]> wrote:
>
>
>
> On Dec 4, 11:44 am, fwc <[EMAIL PROTECTED]> wrote:
> > I successfully upgraded 2.8.14 -> 2.8.15 [Mac OS X 10.4.11, 2 GHz
> > Intel Core 2 Duo, 1 GB].
> >
> > But my worksheets do not appear when I do sage -notebook
Your workshee
On Dec 4, 11:44 am, fwc <[EMAIL PROTECTED]> wrote:
> I successfully upgraded 2.8.14 -> 2.8.15 [Mac OS X 10.4.11, 2 GHz
> Intel Core 2 Duo, 1 GB].
>
> But my worksheets do not appear when I do sage -notebook
>
> I'm told that "The notebook files are stored in: ~/.sage/
> sage_notebook", but the
On 6/8/07, dave dobbs <[EMAIL PROTECTED]> wrote:
> Hi William,
>
> This is a follow-up to my previous reply with two points:
>
> 1. I was in error when I said Reset under the VM pull-down, it's found under
> the Power tab (but I'm sure you knew that.)
>
> 2. I ran into problems when trying to exec
It seemed to work just fine, but then after running a notebook session
the server appears to be locked. After closing Firefox and returning
to the VM session I can move the cursor and keystrokes paint on the
screen, but nothing seems to transmit to the session, not the CNTL-C's
to stop the server
On 6/8/07, davedo2 <[EMAIL PROTECTED]> wrote:
>
> Pardon me if this should be a no brainer, but is it possible to invoke
> the sage -upgrade command using the VMware module or is it necessary
> to download a new VMware module? I tried from within SAGE and Manage
> to no avail...Dave
It is possibl
On 3/31/07, didier deshommes <[EMAIL PROTECTED]> wrote:
> > Hi all. I just upgraded (by running sage -upgrade) and I am having the
> > problem shown down below.
> >
> > Some things that I have tried include running sage with the command
> >
> > LD_LIBRARY_PATH="/home/bober/sage-2.3/local/lib/"
>
On 3/28/07, Jonathan William Bober <[EMAIL PROTECTED]> wrote:
>
> Hi all. I just upgraded (by running sage -upgrade) and I am having the
> problem shown down below.
>
> Some things that I have tried include running sage with the command
>
> LD_LIBRARY_PATH="/home/bober/sage-2.3/local/lib/"
> SAGE
37 matches
Mail list logo
