sage-9.1.beta8 on Ubuntu Linux 20.04 LTS Focal Fossa.
--
You received this message because you are subscribed to the Google Groups
"sage-devel" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to sage-devel+unsubscr...@googlegroups.com.
To view this discuss
sage -upgrade is obsolete and should be removed.
It's better to install a new version from source.
On Sat, Apr 4, 2020 at 12:45 AM Ethan Lin wrote:
>
> Somehow I can seem to upgrade sage with the sage -upgrade command it gives me
> this error: error: cannot open .git/FETCH_HEAD: Permission denie
Somehow I can seem to upgrade sage with the sage -upgrade command it gives
me this error: error: cannot open .git/FETCH_HEAD: Permission denied
--
You received this message because you are subscribed to the Google Groups
"sage-devel" group.
To unsubscribe from this group and stop receiving emai
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 p
On Thursday, August 25, 2011 6:42:30 PM UTC-7, Kevin Horton wrote:
> I suggest that the check for uncommitted changes should be revised to allow
> .DS_Store files that are not known to Mercurial on OS X. Perhaps it should
> allow any unknown files on any platform.
>
Actually, we should ignor
On 2011-08-25, at 20:08 , leif wrote:
> On 25 Aug., 23:04, John H Palmieri wrote:
>> On Thursday, August 25, 2011 9:12:01 AM UTC-7, leif wrote:
>>
>>> On 25 Aug., 16:51, Jeroen Demeyer wrote:
On 2011-08-25 14:40, leif wrote:
>>
> What I can definitely say is that Sage 4.7.1.rc2's hg c
On 2011-08-24, at 13:41 , Maarten Derickx wrote:
> Dear Kevin,
>
> The two commands I gave where intender for RegB who had trouble with the
> untrusted hg message sorry for the confusion.
>
> Well according to your error message sage cannot upgrade since the hg
> repository in /Users/kwh/apps
Dear Kevin,
The two commands I gave where intender for RegB who had trouble with the
untrusted hg message sorry for the confusion.
Well according to your error message sage cannot upgrade since the hg
repository in /Users/kwh/apps/sage has uncommited changes. But if that
doesn't have any chan
On 2011-08-23, at 12:10 , Maarten Derickx wrote:
> I don't know if you are a developer, but it might be possible that you still
> have have queue in one of your repositories. To test this do
>
>sage -hg qdiff
>
> in the different repositories.
>
> Also did you try removing (or beter moving
I'm trying to upgrade sage on two boxes from 4.7 to 4.7.1. "sage -upgrade"
fails with "There are uncommitted changes in the Sage root repository.
Aborting."
On one box, "sage -hg diff" found that I had modified SAGE_ROOT, so I undid
that. But it still complains about uncommitted changes, even
Hi,
WARNING: On Linux, if you do "sage -upgrade" right now, you may need to do
./sage -f numpy-1.3.0.p2.spkg scipy_sandbox-20071020.p4.spkg scipy-0.7.p3.spkg
(or something very similar) to force rebuild of some code that depends
on fortran libraries.
See http://trac.sagemath.org/sage_trac/tick
2010/1/16 Igor Tolkov :
> My SAGE upgrade (using sage --upgrade) on the machine:
What GCC?
Precisely what computer?
What version were you upgrading from?
Post a link to the complete install.log file.
>
> Linux IT 2.6.24-19-generic #1 SMP Wed Aug 20 17:53:40 UTC 2008 x86_64
> GNU/Linux
>
> failed
My SAGE upgrade (using sage --upgrade) on the machine:
Linux IT 2.6.24-19-generic #1 SMP Wed Aug 20 17:53:40 UTC 2008 x86_64
GNU/Linux
failed with the following error:
g++ -o groebner/src/randomset.o -c -O3 -Wno-long-long -Wreturn-type -g
-fPIC -ftemplate-depth-100 -g -fPIC -O3 -Wno-long-long -W
Hi
I build sage from source as I believe someone told me
that you can do the partial downloads of only new SPKGes
with sage -upgrade, but you cannot do this if you untarred a
binary. Correct?
Can I tell sage -upgrade to use a South African mirror?
Are components (SPKGes) mirrored?
regards,
Jan
Hi
sage -upgrade 4.0 to 4.1:
Finished extraction
Host system
uname -a:
Linux hamerkop 2.6.28-13-generic #45-Ubuntu SMP Tue Jun 30 22:12:12 UTC 2009
x86_64 GNU/Linux
***
Hi
sage -upgrade from 3.4.2 to 4.0.1
http://www.sagemath.org//spkg/standard/atlas-3.8.3.p3.spkg -->
atlas-3.8.3.p3.spkg
[..]
Deleting old spkg atlas-3.8.3.p1.spkg
All the SPKGes do this.
NEW -> NEW
..
deleting OLD
instead of
OLD -
Are the sources not in the right spots yet?
- Robert
--~--~-~--~~~---~--~~
To post to this group, send email to sage-devel@googlegroups.com
To unsubscribe from this group, send email to
sage-devel-unsubscr...@googlegroups.com
For more options, visit this group a
Hi,
As some of you know, I have a precious system wide install of sage. The latest
sage -upgrade
brought me to version 3.4:
$ ls /usr/local/sage/spkg/installed/sage-*
sage-1.5.1.2 sage-2.1 sage-2.2 sage-2.6 sage-2.8.3
sage-2.8.8.1 sage-3.1
sage-1.5.3sage-2.10 sage-2
Hi,
I would like to propose again that we deprecate the
sage -upgrade
functionality for "normal end users". It was definitely never
meant to be used by anybody but developers -- in fact I wrote
it mainly for David Kohel (an early Sage developer) who lived
in Australia and consequentl
Hi,
I think I have done "sage -upgrade" a few times when William was in
the process of uploading a new release. I think it would be helpful if
Sage would check a file on sagemath that gave the latest release that
had been completed uploaded. Another possibility might be that William
would upload
bash#sage -upgrade
***Does most things I guess. Throws the following
error**
sage: An error occurred while installing singular-3-0-3-1-20071005
Please email sage-devel http://groups.google.com/group/sage-devel
explaining the problem and send the relevant part of
of /home/kks/sage
I get the following errors:
$ sage -upgrade
Using SAGE Server http://www.sagemath.org//packages
http://www.sagemath.org//packages/install --> install
[.]
http://www.sagemath.org//packages/standard/list --> list
[.]
http://www.sagemath.org//packages/standard/deps --> deps
[..]
http://www.sagemath.
Hello all,
sage -upgrade seems to be blowing away my committed hg patches that
have not been pushed to William yet.
To the best of my memory, that did not happen in the past; has this
changed? Am I doing something wrong? This is getting annoying --
it's very hard to submit patches against up-t
Hi,
I'm trying a "sage -upgrade" to go from v. 2.5.3 to 2.6. I'm getting a
patching error on clisp. It wants a "File to patch". Full transcript in the
P.S. Any ideas how I could resolve this?
I did not try building from scratch using the sage-2.6 tarball. I will try
that now.
--
Joel
Any reason the upgrade keeps old versions of the documentation
around? They are quite big one can have quite a few hanging around
after just a couple of upgrades.
Yi
--~--~-~--~~~---~--~~
To post to this group, send email to sage-devel@googlegroups.com
To
Hi,
sage -upgrade definitely doesn't work because of some issues involving the
base package.
It sucks down the upgraded packages, but won't install them (hence
shouldn't cause any
problems either). So far now a fresh install is required.
William
--~--~-~--~~~---
26 matches
Mail list logo
