On 29 Jun., 04:04, Mike Hansen wrote:
> On Mon, Jun 28, 2010 at 3:07 PM, Georg S. Weber
>
> wrote:
> > I remember that once Michael Abshoff had created some mechanism to
> > make the Sage/Maxima interface (i.e. the pexpect interface in general)
> > produce verbose output into some log files (vi
About a week ago I started getting an infinite redirect when trying to
visit google groups with chrome 5.0.375. What fixed it for me was to
delete all google.groups.com cookies in chrome (Options->Under the
Hood->Content Settings->Show Cookies). Not only can I visit google
groups, I can also open l
Hi all,
this message is cross-posted between the gentoo-science and sage-devel
mailing lists.
So this is sage-4.4.4 and we have come a long way.
sage-on-gentoo is now usable for the majority of people and can be used
to test development ideas.
We have a page where we list our current issues:
htt
> Outstanding issues:
> -singular: we really wish sage would move to the latest upstream.
When we tried to update the last time we found a bug (or change of behaviour)
in the most recent Singular release:
cf. http://trac.sagemath.org/sage_trac/ticket/8059
It is likely that upstream fixed it by
> > Outstanding issues:
> > -singular: we really wish sage would move to the latest upstream.
>
> When we tried to update the last time we found a bug (or change of
> behaviour) in the most recent Singular release:
>
> cf. http://trac.sagemath.org/sage_trac/ticket/8059
>
> It is likely that ups
Hi Volker,
On Jun 29, 9:29 am, Volker Braun wrote:
> About a week ago I started getting an infinite redirect when trying to
> visit google groups with chrome 5.0.375. What fixed it for me was to
> delete all google.groups.com cookies in chrome (Options->Under the
> Hood->Content Settings->Show Co
On 06/29/10 12:03 PM, François Bissey wrote:
Hi all,
this message is cross-posted between the gentoo-science and sage-devel
mailing lists.
So this is sage-4.4.4 and we have come a long way.
sage-on-gentoo is now usable for the majority of people and can be used
to test development ideas.
Good
> I suspect the ONLY sensible way to do that would be to drop in new
> Singular, delete all record of all the patches to singular package, and
> create new patches as and when needed.
You suspect wrong. A new Singular SPKG is available in the ticket I referenced
in this thread which takes care of
On 06/29/10 01:26 PM, Martin Albrecht wrote:
I suspect the ONLY sensible way to do that would be to drop in new
Singular, delete all record of all the patches to singular package, and
create new patches as and when needed.
You suspect wrong. A new Singular SPKG is available in the ticket I refe
On Jun 29, 1:53 am, William Stein wrote:
> Hi,
>
> Does anybody have a clue why users accidentally randomly delete
> Moinmoin pages all the time? This is constantly happening to people
> at Sage Days 22, with all kinds of browsers, networks, etc.
>
> This is very weird. I couldn't find anythin
Thanks, Georg, for clarifying that it's Tiger, not PPC. This ticket
is already open at http://trac.sagemath.org/sage_trac/ticket/9361, and
I will change it accordingly.
- kcrisman
On Jun 29, 3:26 am, "Georg S. Weber"
wrote:
> On 29 Jun., 04:04, Mike Hansen wrote:
>
> > On Mon, Jun 28, 2010 at
> sage-deluxe-4.4.4-i386-Darwin.dmg
> has the "new" application--it should be nicer, but more experimental.
> Please read the README and give me any feedback you have.
>
Thanks, Ivan! This looks like a monstrous improvement on the
surface. Thanks so much for your hard work. I hope my
Hi,
The hard drive that serves the http://sagemath.org website, all
wiki's, etc., stopped working at 3am this morning.
It's in Seattle, and I'm in California.Tom Boothby is the other
person who can work on this stuff, and I haven't
heard from him for a while. Until I do, there will be major
i
On Jun 29, 2010, at 9:08 AM, kcrisman wrote:
>> sage-deluxe-4.4.4-i386-Darwin.dmg
>> has the "new" application--it should be nicer, but more
>> experimental. Please read the README and give me any feedback you have.
>
> Thanks, Ivan! This looks like a monstrous improvement on the
> sur
David,
I just finished building sage-4.4.4.1 as a regular user (not root)
on many of the Skynet Linux machines.
I do not see the error message that you are reporting.
Perhaps this is a problem only on Solaris machines?
Mariah
On Jun 28, 5:50 pm, "Dr. David Kirkby"
wrote:
> I noticed this err
On 06/29/10 04:26 PM, Mariah wrote:
David,
I just finished building sage-4.4.4.1 as a regular user (not root)
on many of the Skynet Linux machines.
I do not see the error message that you are reporting.
Perhaps this is a problem only on Solaris machines?
Mariah
This particular problem may b
>
> > So I made another folder to put it in, copied it there. The same
> > thing happened, even though that folder was otherwise empty - message
> > "You can’t copy “Sage” because it has the same name as another item on
> > the destination volume, and that volume doesn’t distinguish between
> > up
On 06/29/10 03:52 PM, caleb miles wrote:
Hello,
Compiling with gcc-4.3.5 produces the following error
mkdir -p -- ../../../../library/grDevices/libs
make[8]: warning: Clock skew detected. Your build may be incomplete.
That is usually the result of shared file system where the client and se
Hi,
Thanks to some swift work by Tom Boothby, the sagemath.org website,
wiki's, etc., are all back online.
william
On Tue, Jun 29, 2010 at 8:15 AM, William Stein wrote:
> Hi,
>
> The hard drive that serves the http://sagemath.org website, all
> wiki's, etc., stopped working at 3am this morning.
Dear Sage Developers,
I have modified a patch that I proposed a while ago and needed to be
improved and now I've submitted the change, but when I wanted to find
the changeset number (by typing hg_sage.log() ) the first entry was
not my changeset. Moreover, this entry was from January, which I think
The patch is up:
http://trac.sagemath.org/sage_trac/ticket/9376
I haven't tested it thoroughly yet.
--
To post to this group, send an email to sage-devel@googlegroups.com
To unsubscribe from this group, send an email to
sage-devel+unsubscr...@googlegroups.com
For more options, visit this group
On Jun 29, 1:03 pm, François Bissey wrote:
> [..] excellent summary [..]
>
> If have been reading this far - thank you for your time.
> Christopher may add comments on anything that I forgot.
One thing:
- We do not install scipy_sandbox but instead apply the patches from
this ticket: http://trac
Kwankyu,
This is now trac #9377.
sage-support is a better place to report bugs.
sage-devel is for discussions about development.
Mariah
On Jun 28, 10:45 pm, Kwankyu Lee wrote:
> Hi,
>
> On Sage 4.4.4, I have the following bug.
>
> sage: F.=GF(4)
> sage: m=matrix(2,[F(1),2,3,4])
> sage: magma
Dear all,
Does anyone know what is going on here (the double Maxima exit)? It
must have something to do with the sum loading, I guess, since this
doesn't happen with integration (see below). If someone has an older
Sage it would be worth testing to make sure this happens there (this
was all inco
Hello,
I received the same error, relating to the installation of R;
make[6]: Entering directory `/nano/scratch/camiles/binaries/sage-4.4.4/
spkg/build/r-2.10.1.p1/src/src/library/grDevices'
Warning in solve.default(rgb) :
unable to load shared library '/users/camiles/nano-scratch/binaries/
sa
It seems that executing a python script via sage-native-execute can
cause problems, because not everything gets reset:
$ sage -sh
Starting subshell with Sage environment variables set.
Be sure to exit when you are done and do not do anything
with other copies of Sage!
Bypassing shell configurati
I've been chasing my tail much of today, trying to make Singular play ball.
Managed to find out one for for sure. Someone has written a patch to
src/Singular/Makefile.in, then someone else has written one to the same file and
overwrote the first one.
patch()
{
# work-around patches
cp
On Jun 29, 2010, at 10:41 AM, kcrisman wrote:
>>> So I made another folder to put it in, copied it there. The same
>>> thing happened, even though that folder was otherwise empty - message
>>> "You can’t copy “Sage” because it has the same name as another item on
>>> the destination volume, and th
On Jun 29, 2010, at 10:41 AM, kcrisman wrote:
>>> So I made another folder to put it in, copied it there. The same
>>> thing happened, even though that folder was otherwise empty - message
>>> "You can’t copy “Sage” because it has the same name as another item on
>>> the destination volume, and t
This is now http://trac.sagemath.org/sage_trac/ticket/9386
I found that the symptom (with magma) is recent: It's due to the
merger of http://trac.sagemath.org/sage_trac/ticket/8560
--
To post to this group, send an email to sage-devel@googlegroups.com
To unsubscribe from this group, send an email
On Jun 29, 2010, at 5:18 PM, Dr. David Kirkby wrote:
> I've been chasing my tail much of today, trying to make Singular play ball.
> Managed to find out one for for sure. Someone has written a patch to
> src/Singular/Makefile.in, then someone else has written one to the same file
> and overwro
> On Jun 29, 2010, at 5:18 PM, Dr. David Kirkby wrote:
> > I've been chasing my tail much of today, trying to make Singular play
> > ball. Managed to find out one for for sure. Someone has written a patch
> > to src/Singular/Makefile.in, then someone else has written one to the
> > same file and o
On Jun 29, 4:13 pm, François Bissey wrote:
> sage doesn't assume that the patch command is installed but rely on cp being
> there. That's why patch aren't used.
> I agree not ideal but that's a lowest common denominator issue.
Perhaps compare the md5sum of the original and bail if it's not the
ex
> On Jun 29, 4:13 pm, François Bissey wrote:
> > sage doesn't assume that the patch command is installed but rely on cp
> > being there. That's why patch aren't used.
> > I agree not ideal but that's a lowest common denominator issue.
>
> Perhaps compare the md5sum of the original and bail if it'
> I've been chasing my tail much of today, trying to make Singular play ball.
> Managed to find out one for for sure. Someone has written a patch to
> src/Singular/Makefile.in, then someone else has written one to the same
> file and overwrote the first one.
>
What we need here is probably a stan
I just want to call attention here in sage-devel to what I consider to
be an important bug:
http://trac.sagemath.org/sage_trac/ticket/9385
I'm compiling Sage in a fedora 13 Intel Core Duo laptop (1.8 Gb RAM). It
normally takes about 6 hours to build previous versions of sage,
however, it now
I'm surprised you don't use patch.
Mercurial can generate patches.
François Bissey wrote:
On Jun 29, 4:13 pm, François Bissey wrote:
sage doesn't assume that the patch command is installed but rely on cp
being there. That's why patch aren't used.
I agree not ideal but that's a lowest comm
On 06/30/10 12:54 AM, Tim Daly wrote:
I'm surprised you don't use patch.
Mercurial can generate patches.
That would only be ok at the point Mercurial is built, so might be tricky.
GNU patch is only 200 kB of source code. If we added 200 KB and removed all the
duplicate files (leaving only pat
On 06/30/10 12:39 AM, François Bissey wrote:
On Jun 29, 4:13 pm, François Bissey wrote:
sage doesn't assume that the patch command is installed but rely on cp
being there. That's why patch aren't used.
I agree not ideal but that's a lowest common denominator issue.
Perhaps compare the md5sum
On Tue, Jun 29, 2010 at 4:54 PM, Tim Daly wrote:
> I'm surprised you don't use patch.
> Mercurial can generate patches.
The issue is not generating the patches -- it's applying them. All of
the spkgs (should) have the diff as well as the file with the patch
applied.
--Mike
--
To post to this
On 06/30/10 12:20 AM, Nils Bruin wrote:
On Jun 29, 4:13 pm, François Bissey wrote:
sage doesn't assume that the patch command is installed but rely on cp being
there. That's why patch aren't used.
I agree not ideal but that's a lowest common denominator issue.
Perhaps compare the md5sum of th
Perhaps I'm being thick about this. In Axiom's build
we have a zip file for GCL source code. At build time
we unzip the GCL source, THEN apply our patches, THEN
we do a build.
Why wouldn't this process work in Sage?
Sage requires all of GCC to be installed.
Surely requiring patch is not a lot mo
On Tue, Jun 29, 2010 at 5:25 PM, Tim Daly wrote:
> Perhaps I'm being thick about this. In Axiom's build
> we have a zip file for GCL source code. At build time
> we unzip the GCL source, THEN apply our patches, THEN
> we do a build.
>
> Why wouldn't this process work in Sage?
This is basically wh
On 06/30/10 01:02 AM, Mike Hansen wrote:
On Tue, Jun 29, 2010 at 4:54 PM, Tim Daly wrote:
I'm surprised you don't use patch.
Mercurial can generate patches.
The issue is not generating the patches -- it's applying them. All of
the spkgs (should) have the diff as well as the file with the pat
On Tue, Jun 29, 2010 at 5:31 PM, Dr. David Kirkby
wrote:
> I can't myself see what we gain having the diff and the modified version.
> Even if we stick to using 'cp' (which is a bad idea in my opinion), I would
> much rather create the diff myself if I want to see it.
The modified version is for
On 06/30/10 01:38 AM, Mike Hansen wrote:
On Tue, Jun 29, 2010 at 5:31 PM, Dr. David Kirkby
wrote:
I can't myself see what we gain having the diff and the modified version.
Even if we stick to using 'cp' (which is a bad idea in my opinion), I would
much rather create the diff myself if I want t
On Tue, Jun 29, 2010 at 5:57 PM, Dr. David Kirkby
wrote:
> But if there are two three files
>
> src/foo.c
> patches/foo.c
> patches/foo.c.diff
>
> what does patches/foo.c.diff possibly give me that could could get by
> running
>
> diff src/foo.c patches/foo.c ?
This requires that patches/foo.c wa
We use a naming convention for patches.
Thus the 3rd new patch created today by me would have the name:
20100629.03.tpd.patch
which orders the patches by date, sub-sequence, and author.
You might want to use your spkg name instead as in:
20100629.03.singular.patch
This would ensure that patche
Reference the picture:
http://diffusion.cgu.edu.tw/ftp/sage-4.4.4.lzm
Sage runs on both on web (firefox) and TeXmacs
download site:
http://diffusion.cgu.edu.tw/ftp/sage-4.4.4.iso
md5: 3fe488d138e04cac70e888a2d74d6537
How to make a bootable USB version:
Copy all the files to USB
> boot/boot_in
> This is now trac #9377.
Thank you.
> sage-support is a better place to report bugs.
> sage-devel is for discussions about development.
>
> Mariah
I see.
Kwankyu
--
To post to this group, send an email to sage-devel@googlegroups.com
To unsubscribe from this group, send an email to
sage-deve
On Jun 30, 2:59 am, cch wrote:
> Reference the picture:http://diffusion.cgu.edu.tw/ftp/sage-4.4.4.lzm
>
Correction:
http://diffusion.cgu.edu.tw/ftp/sage-4.4.4.png
--
To post to this group, send an email to sage-devel@googlegroups.com
To unsubscribe from this group, send an email to
sage-deve
51 matches
Mail list logo
