On Mar 5, 2008, at 7:55 AM, mabshoff wrote:
> The merge goes on. 2.10.3.rc2 can be found at
>
> http://sage.math.washington.edu/home/mabshoff/release-cycles-2.10.3/
> sage-2.10.3.rc2.tar
Built on two 10.4 systems, with slightly different results. The
build succeeded in each case, but the te
This fails to compile on my intel mac (10.4.11), but its the same R
failure I had with rc0. I have not tried William's suggestion of
upgrading my gcc, I'll give that a shot tomorrow.
-M. Hampton
On Mar 5, 9:55 am, mabshoff <[EMAIL PROTECTED]
dortmund.de> wrote:
> The merge goes on. 2.10.3.rc2 c
On Wed, Mar 5, 2008 at 3:16 PM, David Joyner <[EMAIL PROTECTED]> wrote:
>
> On Wed, Mar 5, 2008 at 6:14 PM, William Stein <[EMAIL PROTECTED]> wrote:
> >
> > On Wed, Mar 5, 2008 at 3:13 PM, David Joyner <[EMAIL PROTECTED]> wrote:
> > >
> > > On an amd64 bit ubuntu 7.04 linux machine:
> >
On Wed, Mar 5, 2008 at 6:14 PM, William Stein <[EMAIL PROTECTED]> wrote:
>
> On Wed, Mar 5, 2008 at 3:13 PM, David Joyner <[EMAIL PROTECTED]> wrote:
> >
> > On an amd64 bit ubuntu 7.04 linux machine:
> >
> > The following tests failed:
> >
> >
> > sage -t devel/sage-main/sage/fu
On Wed, Mar 5, 2008 at 3:13 PM, David Joyner <[EMAIL PROTECTED]> wrote:
>
> On an amd64 bit ubuntu 7.04 linux machine:
>
> The following tests failed:
>
>
> sage -t devel/sage-main/sage/functions/orthogonal_polys.py
> sage -t devel/sage-main/sage/rings/polynomial/groebner_fan.p
On an amd64 bit ubuntu 7.04 linux machine:
The following tests failed:
sage -t devel/sage-main/sage/functions/orthogonal_polys.py
sage -t devel/sage-main/sage/rings/polynomial/groebner_fan.py
sage -t devel/sage-main/sage/matrix/matrix_symbolic_dense.pyx
sage -
mabshoff wrote:
> The merge goes on. 2.10.3.rc2 can be found at
>
> http://sage.math.washington.edu/home/mabshoff/release-cycles-2.10.3/sage-2.10.3.rc2.tar
>
> A sage.math binary for those interested in not
> compiling all of Sage is at
>
> http://sage.math.washington.edu/home/mabshoff/release-
Hi,
Regarding 2.10.2.rc2 the failures are as follows:
32-bit linux ubuntu:
sage -t devel/sage-main/sage/matrix/matrix_symbolic_dense.pyx
sage -t devel/sage-main/sage/plot/plot.py
sage -t devel/sage-main/sage/structure/factorization.py
sage -t devel/sage-main/
2.10.3.rc2 built ok on
[EMAIL PROTECTED] -a
Linux host-57-71 2.6.18.8-0.3-default #1 SMP Tue Apr 17 08:42:35 UTC
2007 x86_64 x86_64 x86_64 GNU/Linux
[EMAIL PROTECTED] -v
Using built-in specs.
Target: x86_64-suse-linux
Configured with: ../configure --enable-threads=posix --prefix=/usr
--with-local
Mabshoff,
In rc2, I get that glibc problem sometimes when simply exiting the
program:
"""
[EMAIL PROTECTED]:~/sage-2.10.3.rc2-sage.math-only-x86_64-Linux$ ./sage
--
| SAGE Version 2.10.3.rc2, Release Date: 2008-03-05
On Feb 25, 9:53 pm, philt <[EMAIL PROTECTED]> wrote:
> > In between the upgrade to 2.10.1 did you change anything like the gcc
> > version?
>
> No
>
> > #define __LINBOX_CONFIGURATION
> > #include "linbox/config-blas.h"
> > int main ()
> > {
> > double a;
> > return 0;
>
> > }
>
> > If that wo
> In between the upgrade to 2.10.1 did you change anything like the gcc
> version?
No
> #define __LINBOX_CONFIGURATION
> #include "linbox/config-blas.h"
> int main ()
> {
> double a;
> return 0;
>
> }
>
> If that work we have a problem somewhere, if it doesn't work something
> it wrong with yo
>
> While I have
> local/lib/libcblas.so
Ok, is that $SAGE_LOCAL/local/lib ? The config test complains about a
missing cblas:
configure:24249: g++ -o conftest -g -fPIC -I"/opt/sage-2.10/local/
include" -I"/opt/sage-2.10/local/include/linbox"
-L"/opt/sage-2.10/local/lib" -g -I"/opt/sage-2.10/
Hi Michael,
> Does this happen reproducibly?
I tried twice "sage -upgrade" and twice the same error (looks like it
tries twice per attempt then stops)
> I assume you are on Linux, but which
> distribution, CPU type, gcc and so on?
64-bit Debian Lenny in a vserver
sage:/# uname -a
Linux sage 2.6
On Feb 24, 3:05 pm, philt <[EMAIL PROTECTED]> wrote:
> sage -upgrade from 2.10.1 to 2.10.2:
> I got a failure here:
Hi Phil.
Does this happen reproducibly? I assume you are on Linux, but which
distribution, CPU type, gcc and so on?
> package /opt/sage-2.10/spkg/standard/linbox-20070915.p6.sp
sage -upgrade from 2.10.1 to 2.10.2:
I got a failure here:
package /opt/sage-2.10/spkg/standard/linbox-20070915.p6.spkg
checking for NTL >= 5.0... found
checking for GIVARO >= 3.0... found
checking for C interface to BLAS... not found
checking for others BLAS... not found
**
I am having trouble as described in trac # 2003; I had the same
problem with 2.10.1 but I don't have a serious reason to use the
latest sage on my laptop, so I just waited and hoped it would get
fixed for 2.10.2.
I tried changing my path to something pretty minimal but I am still
having this prob
On Sat, Feb 23, 2008 at 11:26 AM, mabshoff <[EMAIL PROTECTED]> wrote:
...
> it always takes a while (roughly up to a day) for the binaries to be
> build, tested and uploaded to the sagemath.org. So they should appear
> this evening.
>
> Cheers,
>
> Michael
I see. Thanks for letting me know,
Hi Hector,
> I just noticed that the binary downloads for sage-2.10.2 haven't been
> updated, just the source code is available.
> Best,
> --
> Hector
it always takes a while (roughly up to a day) for the binaries to be
build, tested and uploaded to the sagemath.org. So they should appear
this
On Sat, Feb 23, 2008 at 10:17 AM, William Stein <[EMAIL PROTECTED]> wrote:
>
> On Sat, Feb 23, 2008 at 7:21 AM, mabshoff <[EMAIL PROTECTED]> wrote:
> >
> >
> >
> > On Feb 23, 3:48 am, "William Stein" <[EMAIL PROTECTED]> wrote:
> > > Hello folks,
> > >
> > > Sage 2.10.2 has been release
On Sat, Feb 23, 2008 at 7:21 AM, mabshoff <[EMAIL PROTECTED]> wrote:
>
>
>
> On Feb 23, 3:48 am, "William Stein" <[EMAIL PROTECTED]> wrote:
> > Hello folks,
> >
> > Sage 2.10.2 has been released on February 23nd, 2008. It is available at
> >
> >http://sagemath.org/download.html
>
On Feb 23, 3:48 am, "William Stein" <[EMAIL PROTECTED]> wrote:
> Hello folks,
>
> Sage 2.10.2 has been released on February 23nd, 2008. It is available at
>
>http://sagemath.org/download.html
Those of you who want to bundle patches against 2.10.2 be warned that
currently the repo a
Done.
On 22/02/2008, mabshoff <[EMAIL PROTECTED]> wrote:
>
>
>
> On Feb 22, 11:20 pm, "John Cremona" <[EMAIL PROTECTED]> wrote:
> > Built ok (kubuntu 7.70, gcc version 4.1.3 20070929 (prerelease)
> > (Ubuntu 4.1.2-16ubuntu2))
>
>
> Hi John,
>
>
> > The following tests failed:
> >
> >
On Feb 22, 11:20 pm, "John Cremona" <[EMAIL PROTECTED]> wrote:
> Built ok (kubuntu 7.70, gcc version 4.1.3 20070929 (prerelease)
> (Ubuntu 4.1.2-16ubuntu2))
Hi John,
> The following tests failed:
>
> sage -t devel/sage-main/sage/rings/number_field/number_field.py
> sage -t de
Built ok (kubuntu 7.70, gcc version 4.1.3 20070929 (prerelease)
(Ubuntu 4.1.2-16ubuntu2))
The following tests failed:
sage -t devel/sage-main/sage/rings/number_field/number_field.py
sage -t devel/sage-main/sage/rings/number_field/number_field_ideal.py
Total time for all tests
On Feb 22, 8:52 pm, David Harvey <[EMAIL PROTECTED]> wrote:
> On Feb 22, 2008, at 2:43 PM, mabshoff wrote:
>
> > Hi David,
Hi David,
> > I poked around in the install log and the issue is "Resource
> > temporarily unavailable", i.e. the dreaded OSX resource limits that
> > are too low. A sugge
On Feb 22, 2008, at 2:43 PM, mabshoff wrote:
> Hi David,
>
> I poked around in the install log and the issue is "Resource
> temporarily unavailable", i.e. the dreaded OSX resource limits that
> are too low. A suggested fix is at
>
> http://wiki.sagemath.org/Tips
Thanks, well spotted!
> So: no
On Feb 22, 4:21 pm, David Harvey <[EMAIL PROTECTED]> wrote:
> On Feb 22, 2008, at 8:29 AM, Michael.Abshoff wrote:
>
> > Could you please post slightly more of the log? It looks like it
> > happens
> > during "make install" which would make it easy to fix. Is it
> > reproducible?
>
> http://sage.
On Feb 22, 10:45 am, "Craig Citro" <[EMAIL PROTECTED]> wrote:
> > this is 2.10.2.rc0, which hopefully will be identical to 2.10.2
> > final.
>
> I got four doctest failures on my OSX Intel 10.5 box:
>
> sage -t devel/sage-main/sage/calculus/calculus.py
> sage -t devel/sage-ma
On Feb 22, 8:29 am, "Michael.Abshoff" <[EMAIL PROTECTED]>
wrote:
> Could you please post slightly more of the log? It looks like it happens
> during "make install" which would make it easy to fix. Is it reproducible?
I built again with -j1, now the build was fine. I'm going to run
doctests on
On Feb 22, 6:37 pm, bill purvis <[EMAIL PROTECTED]> wrote:
> On Friday 22 February 2008, Craig Citro wrote:> > this is 2.10.2.rc0, which
> hopefully will be identical to 2.10.2
> > > final.
>
> > I got four doctest failures on my OSX Intel 10.5 box:
>
> > sage -t devel/sage-main/sage
On Friday 22 February 2008, Craig Citro wrote:
> > this is 2.10.2.rc0, which hopefully will be identical to 2.10.2
> > final.
>
> I got four doctest failures on my OSX Intel 10.5 box:
>
> sage -t devel/sage-main/sage/calculus/calculus.py
> sage -t devel/sage-main/sage/rings/num
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Nothing extraordinary: built and tested on dual core
laptop running Gentoo. Everything is ok except for the
two number_field test failures already reported by others.
Best,
Alex
mabshoff wrote:
| Hello folks,
|
| this is 2.10.2.rc0, which hopefull
> Here are the pow_computer failures:
> sage -t devel/sage-main/sage/rings/padics/pow_computer.pyx
> **
> File "pow_computer.pyx", line 160:
>sage: PC._pow_mpz_t_tmp_demo(6, 8)
> Expected:
>244140625
> Got:
>1525878906
Problems with sage-2.10.2.rc0:
1. One 32-bit REDHAT, 32-bit Debian (minimal),
The build completely fails at the "sage -br" part with:
...
sage/misc/sage_timeit_class.pyx -->
/home/was/build/sage-2.10.2.rc0/local//lib/python/site-packages//sage/misc/sage_timeit_class.pyx
running install
running bu
On Feb 22, 2008, at 8:29 AM, Michael.Abshoff wrote:
> Could you please post slightly more of the log? It looks like it
> happens
> during "make install" which would make it easy to fix. Is it
> reproducible?
http://sage.math.washington.edu/home/dmharvey/install.log.gz
I am going to try buil
David Harvey wrote:
> On Feb 21, 2008, at 10:15 PM, mabshoff wrote:
>
>> Hello folks,
>>
>> this is 2.10.2.rc0, which hopefully will be identical to 2.10.2
>> final.
>> Please build and doctest this release and report any issue you
>> come across. At this point only critical issues will be patche
On Feb 21, 2008, at 10:15 PM, mabshoff wrote:
>
> Hello folks,
>
> this is 2.10.2.rc0, which hopefully will be identical to 2.10.2
> final.
> Please build and doctest this release and report any issue you
> come across. At this point only critical issues will be patched,
> i.e. doctest failures o
> this is 2.10.2.rc0, which hopefully will be identical to 2.10.2
> final.
I got four doctest failures on my OSX Intel 10.5 box:
sage -t devel/sage-main/sage/calculus/calculus.py
sage -t devel/sage-main/sage/rings/number_field/number_field.py
sage -t devel/sage-main
OK -- I found these responses only on Friday morning (GMT) and had not
done anything about them anyway.
I was going to suggest replacing the code with
sage: A, gens = E.abelian_group(); A
Multiplicative Abelian Group isomorphic to C5
with a remark in the text that the actual generators sho
On Feb 22, 12:04 am, "John Cremona" <[EMAIL PROTECTED]> wrote:
> alpha2 built fine for me
>
> make check found this:
Hi John,
> sage -t const.tex
> **
> File "const.py", line 3200:
> : G = E.abelian_group(); G
> Expected:
On Thu, Feb 21, 2008 at 3:04 PM, John Cremona <[EMAIL PROTECTED]> wrote:
>
> alpha2 built fine for me
>
> make check found this:
>
> sage -t const.tex
> **
>
> File "const.py", line 3200:
> : G = E.abelian_group(); G
> E
alpha2 built fine for me
make check found this:
sage -t const.tex
**
File "const.py", line 3200:
: G = E.abelian_group(); G
Expected:
(Multiplicative Abelian Group isomorphic to C5, ((1 : 0 : 1),))
Got:
(Multiplicat
On Thursday 21 February 2008, mabshoff wrote:
> Here we go with 2.10.2.alpha2. It fixes a whole bunch of doctest
> failures
> and also finishes the merging of the graph theory code.
>
> The tarball [209MB] is available at the usual place:
>
> http://sage.math.washington.edu/home/mabshoff/release-c
On Wed, Feb 20, 2008 at 8:57 PM, <[EMAIL PROTECTED]> wrote:
>
> ??? Either I've got a doppelganger, I've been fixing Sage bugs in my sleep,
> or this was misattributed...
You mean you haven't seen my long red braided hair? :)
--
Bobby Moretti
[EMAIL PROTECTED]
--~--~-~--~~--
That's weird. Obviously I would not have poseted the patches at all
if they had not passed all tests on my machine.
Anyway, by the time I came home and could read email you and William
had fixed it all, so thanks a lot for that -- and next time i'll try
to make it easier.
John
On 21/02/2008, m
mabshoff wrote:
> Here we go with 2.10.2.alpha2. It fixes a whole bunch of doctest
> failures
> and also finishes the merging of the graph theory code.
>
> The tarball [209MB] is available at the usual place:
>
> http://sage.math.washington.edu/home/mabshoff/release-cycles-2.10.2/sage-2.10.2.alp
On Wed, Feb 20, 2008 at 8:36 PM, mabshoff
<[EMAIL PROTECTED]> wrote:
>
> Here we go with 2.10.2.alpha2. It fixes a whole bunch of doctest
> failures
> and also finishes the merging of the graph theory code.
>
> The tarball [209MB] is available at the usual place:
>
>
> http://sage.math.washi
On Feb 21, 10:24 am, "John Cremona" <[EMAIL PROTECTED]> wrote:
> Michael,
>
> Is there anything I can do to help with 1946? It's now a month since
> I wrote that stuff and the more releases that go by before it is
> merged the harder it will be. Or will it be easier (for you!) to wait
> until
On Feb 21, 6:36 am, "William Stein" <[EMAIL PROTECTED]> wrote:
> On Wed, Feb 20, 2008 at 8:57 PM, <[EMAIL PROTECTED]> wrote:
>
> > #1366: Tom Boothby: speed up "sage -br" - cache the dependency
> > diagram instead of computing it every time
>
> > ??? Either I've got a doppelganger, I'
Michael,
Is there anything I can do to help with 1946? It's now a month since
I wrote that stuff and the more releases that go by before it is
merged the harder it will be. Or will it be easier (for you!) to wait
until 2.10.2 is released without it and then redo the patch based on
that?
John
On Wed, Feb 20, 2008 at 8:57 PM, <[EMAIL PROTECTED]> wrote:
>
> #1366: Tom Boothby: speed up "sage -br" - cache the dependency
> diagram instead of computing it every time
>
> ??? Either I've got a doppelganger, I've been fixing Sage bugs in my sleep,
> or this was misattributed...
>
#1366: Tom Boothby: speed up "sage -br" - cache the dependency
diagram instead of computing it every time
??? Either I've got a doppelganger, I've been fixing Sage bugs in my sleep, or
this was misattributed...
On Wed, 20 Feb 2008, mabshoff wrote:
>
> Here we go with 2.10.2.alpha2. It
Hi, all,
On Feb 14, 2008, at 22:41 , mabshoff wrote:
> here is the first alpha0 for 2.10.2. It has been greatly delayed by
> SD7
> and then at least on my end by the cold I brought home from it that
> put
> me out of commission for two days. The big changes in this release
> are
>
> * Debianiza
Craig Citro wrote:
As follow up:
>
> If anyone else is seeing this doctest failure, could you also try it
> out? (I don't see it on my machine, so I'm guessing this works, but I
> can't be sure.)
>
> Patch is here:
>
> http://trac.sagemath.org/sage_trac/ticket/2201
>
I applied the patch by ha
Craig Citro wrote:
> Hi Jaap,
>
> I went ahead and fixed (I hope!) the doctest below. (I just added a
> prec flag, and made the doctests use it, so this should avoid any sort
> of architecture-dependent issues). Could you try this out and let me
> know if it works, and then give the patch a posit
Hi Jaap,
I went ahead and fixed (I hope!) the doctest below. (I just added a
prec flag, and made the doctests use it, so this should avoid any sort
of architecture-dependent issues). Could you try this out and let me
know if it works, and then give the patch a positive review? Thanks!
If anyone
Craig Citro wrote:
>> sage -t devel/sage-main/sage/rings/number_field/number_field.py
>>
>
> Actually, this one could be unexpected numerical noise from the code I
> added in with John Voight's code. Jaap, could you post this doctest
> failure, too?
>
Sorry I missed this message. See
mabshoff wrote:
>
>>> The patch at
>>> http://trac.sagemath.org/sage_trac/attachment/ticket/1963/Sage-2.10.2...
>>> fixes the import error.
>
> Hi Jaap
>
>> After applying the patch I got on Fedora 7 32 bits:
>> --
>> The follo
If you want to commit to the devel/sage repo you need to drop in the
files from
http://sage.math.washington.edu/home/mabshoff/missing-debian.tar.gz
into SAGE_ROOT/devel/sage. hg status should then show that everything
is ok.
Cheers,
Michael
--~--~-~--~~~---~--~~
> sage -t devel/sage-main/sage/rings/number_field/number_field.py
>
Actually, this one could be unexpected numerical noise from the code I
added in with John Voight's code. Jaap, could you post this doctest
failure, too?
-cc
--~--~-~--~~~---~--~~
To pos
On Feb 15, 9:21 pm, "David Roe" <[EMAIL PROTECTED]> wrote:
Hi David,
> This is doctest where the result used to be
> Traceback (most recent call
> last):
>
> ...
>
> TypeError: cannot create a p-adic out of sage.rings.polynomial.multi_polynomial_element.MPolynomial_polydict'>
>
> but after th
This is doctest where the result used to be
Traceback (most recent call
last):
...
TypeError: cannot create a p-adic out of
but after the p-adics patch it started working and returning p. I looked at
it briefly and couldn't figure out why it was doing so.
David
On Fri, Feb 15, 2008 at 3:16 PM
mabshoff wrote:
>
>> sage -t devel/sage-main/sage/rings/polynomial/multi_polynomial.pyx
>
> That is a new one. Could you post the detailed failure?
>
[EMAIL PROTECTED] sage-2.10.2.alpha0]$ ./sage -t
devel/sage-main/sage/rings/polynomial/multi_polynomial.pyx
sage -t
devel/sage-m
> > The patch at
>
> >http://trac.sagemath.org/sage_trac/attachment/ticket/1963/Sage-2.10.2...
>
> > fixes the import error.
Hi Jaap
> After applying the patch I got on Fedora 7 32 bits:
> --
> The following tests failed:
>
>
mabshoff wrote:
>
>
> On Feb 15, 2:03 pm, mabshoff <[EMAIL PROTECTED]
> dortmund.de> wrote:
>> Hello folks,
>>
>>> * unramified and eisenstein extensions
>> We are having some problems with the build from vanilla sources build:
>>
>> [10:11] mabshoff: You there?
>> [10:13] After building alph
On Feb 15, 2:03 pm, mabshoff <[EMAIL PROTECTED]
dortmund.de> wrote:
> Hello folks,
>
> > * unramified and eisenstein extensions
>
> We are having some problems with the build from vanilla sources build:
>
> [10:11] mabshoff: You there?
> [10:13] After building alpha0, I get the following:
> [
Hello folks,
> * unramified and eisenstein extensions
We are having some problems with the build from vanilla sources build:
[10:11] mabshoff: You there?
[10:13] After building alpha0, I get the following:
[10:13] : No module
named padic_extension_generic_element
[10:26] wstein-grant: You
68 matches
Mail list logo
