Re: [sage-release] Re: Sage 7.1.rc0 released

2/2016 12:54 AM, Andrey Novoseltsev wrote: > > On Friday, 11 March 2016 03:08:47 UTC-7, Volker Braun wrote: > > > > I've seen that before on the buildbot. The doctest in question > > generates a random cone, it might randomly pick a very hard problem > >

[sage-release] Re: Sage 7.1.rc0 released

I've seen that before on the buildbot. The doctest in question generates a random cone, it might randomly pick a very hard problem (even though we should be fixing the random seed). I haven't had time to investigate. On Friday, March 11, 2016 at 8:49:16 AM UTC+1, Emmanuel Charpentier wrote: >

[sage-release] Re: Sage 7.0 released

inc] Error 1 > > make[5]: *** [all-stage1-gcc] Error 2 > > make[4]: *** [stage1-bubble] Error 2 > > make[3]: *** [all] Error 2 > > > real 6m28.766s > > user 4m59.615s > > sys 1m11.163s > > ******

[sage-release] Re: Sage 7.0 released

6.0 (clang-600.0.57) (based on LLVM 3.5svn) > > looks very strange; Sage is not built using clang... > > > On Tuesday, January 19, 2016 at 2:21:53 PM UTC, Volker Braun wrote: >> >> The "master" git branch has been updated to Sage-7.0. As always, you can >> ge

Re: [sage-release] Re: Sage 7.0 released

The openat(2) was introduced in OSX 10.10, so the error that it cannot be found in libSystem.B.dylib is factual. Can you check that we compile for the right version? Whats the output of: $ sage -sh $ echo $MACOSX_DEPLOYMENT_TARGET We don't have any OSX 10.9 machines to test; In any case Apple

[sage-release] Sage-7.1.beta6 released

As always, you can get the latest beta version from the "develop" git branch. Alternatively, the self-contained source tarball is at http://www.sagemath.org/download-latest.html a3afb47 Updated Sage version to 7.1.beta6 29282de Trac #19919: upgrade nauty to version 26 and make it standard

Re: [sage-release] Sage 7.1.beta5 released

Its up now! On Thursday, February 25, 2016 at 10:24:37 PM UTC+1, François wrote: > > I am not seeing it yet on github, have you prepared it from your fork? > > Francois > > On 02/26/16 10:14, Volker Braun wrote: > > As always, you can get the latest beta versio

[sage-release] Sage 7.1.beta5 released

As always, you can get the latest beta version from the "develop" git branch. Alternatively, the self-contained source tarball is at http://www.sagemath.org/download-latest.html 190a7be Updated Sage version to 7.1.beta5 7c6e7e0 Trac #19666: Guruswami-Sudan decoder for GRS codes f280bad Trac

[sage-release] Sage 7.1.beta4 released

As always, you can get the latest beta version from the "develop" git branch. Alternatively, the self-contained source tarball is at http://www.sagemath.org/download-latest.html edcb48a Updated Sage version to 7.1.beta4 e4f9a5c Trac #20051: Singularity analysis: fix and speed up singularity

[sage-release] Re: Sage 7.1.beta3 released

Done, and I tested the app and it works for me. On Friday, February 12, 2016 at 6:24:15 PM UTC+1, Dima Pasechnik wrote: > > Hi Volker, > could you build and post somewhere the app version of OSX 10.11, for > testing the installation? > > On Thursday, February 11, 2016 at 9:02

[sage-release] Sage 7.1.beta3 released

As always, you can get the latest beta version from the "develop" git branch. Alternatively, the self-contained source tarball is at http://www.sagemath.org/download-latest.html aabd093 Updated Sage version to 7.1.beta3 e485cc1 Trac #20037: tornado depends on singledispatch 83255cf Trac #20033:

Re: [sage-release] Sage 7.0 released

Are you sure you are not running out of memory in the doc build? You need > 2gb / process. -- You received this message because you are subscribed to the Google Groups "sage-release" group. To unsubscribe from this group and stop receiving emails from it, send an email to

[sage-release] Sage Fedora RPM

I'm working automating distribution packaging with our binary builds. There is now an experimental sage rpm package for Fedora 23 at http://files.sagemath.org/linux/64bit/sagemath-7.1.beta1-1.x86_64.rpm The rpm installs to /opt/SageMath and doesn't add a link anywhere in the path, so you need

[sage-release] Sage 7.1.beta2 released

As always, you can get the latest beta version from the "develop" git branch. Alternatively, the self-contained source tarball is at http://www.sagemath.org/download-latest.html bcb68d0 Updated Sage version to 7.1.beta2 ee7b443 Trac #19992: Upgrade pari_jupyter to 1.1.0 4b99bc8 Trac #19994:

[sage-release] Re: recent woes with relocation of SageMath installation directory

Is this the Ubuntu PPA? I think thats not working right now. Whoever is maintaining it (Jan?) should probably revert it until its fixed. On Tuesday, February 2, 2016 at 6:16:08 PM UTC+1, Samuel Lelievre wrote: > > Dear sage-support (cc: sage-release, sage-devel) > (please reply on

Re: [sage-release] 7.1.beta1 released

This is now fixed in http://trac.sagemath.org/ticket/19984 (needs review) -- You received this message because you are subscribed to the Google Groups "sage-release" group. To unsubscribe from this group and stop receiving emails from it, send an email to

Re: [sage-release] 7.1.beta1 released

On Saturday, January 30, 2016 at 9:28:06 AM UTC+1, Jeroen Demeyer wrote: > > How should sage-fix-pkg-checksums then figure out what the right tarball > is? I see no other way than just guessing... > The mapping package <-> tarball is uniquely determined by checksums.ini and package_version.txt,

[sage-release] 7.1.beta1 released

As always, you can get the latest beta version from the "develop" git branch. Alternatively, the self-contained source tarball is at http://www.sagemath.org/download-latest.html 2505dbc Updated Sage version to 7.1.beta1 a62f35e Trac #19973: More trouble with immutable graphs 993cf5a Trac

[sage-release] Sage 7.0 virtual appliance

The Sage 7.0 virtual appliance can now be found at http://files.sagemath.org/win/index.html Starting with this version, the Jupyter notebook is the default. Not only is it a modern user interface, it also gives you easy access to a shell inside the VM without cryptic key combinations. --

[sage-release] Re: Sage 7.0 released

I've deleted the Sage-7.0 OSX binaries On Tuesday, January 19, 2016 at 9:21:53 AM UTC-5, Volker Braun wrote: > > The "master" git branch has been updated to Sage-7.0. As always, you can > get the latest beta version from the "develop" git branch. Alternatively,

Re: [sage-release] Re: Sage 7.0 virtual appliance

On Tuesday, January 26, 2016 at 7:41:28 PM UTC-5, kcrisman wrote: > > One thing I should have asked on that ticket is whether it's possible to >> test it without any impact on .sage/sage_notebook.sagenb, and then to kill >> the new ipynb files to test again in a different configuration or

[sage-release] Re: Sage 7.0 released

The binaries are now on the file server -- You received this message because you are subscribed to the Google Groups "sage-release" group. To unsubscribe from this group and stop receiving emails from it, send an email to sage-release+unsubscr...@googlegroups.com. To post to this group, send

[sage-release] Sage 7.1.beta0 released

As always, you can get the latest beta version from the "develop" git branch. Alternatively, the self-contained source tarball is at http://www.sagemath.org/download-latest.html d941d8d Updated Sage version to 7.1.beta0 50e8ada Trac #19778: McFarland 1973 construction for difference sets

[sage-release] Re: error: Cannot perform incremental update

After you run "make distclean & make", is lib64 a symlink? If its not then its a bug. On Thursday, January 14, 2016 at 7:32:55 AM UTC+1, Nathann Cohen wrote: > > Hello everybody, > > For the latest beta releases, each time 'git pull && make' produced > the following message: > > ... >

Re: [sage-release] Re: error: Cannot perform incremental update

If "make distclean" fails then its not going to do anything, duh. Delete SAGE_LOCAL by hand or "git clean -f -d -x" On Thursday, January 14, 2016 at 9:22:54 AM UTC+1, Nathann Cohen wrote: > > > After you run "make distclean & make", is lib64 a symlink? If its not > then > > its a bug. > >

[sage-release] Sage 7.0.rc1 released

As always, you can get the latest beta version from the "develop" git branch. Alternatively, the self-contained source tarball is at http://www.sagemath.org/download-latest.html As mentioned before, there are no incremental updates from 6.x. You need to compile from scratch, e.g. after

[sage-release] Sage 7.0.rc0 released

As always, you can get the latest beta version from the "develop" git branch. Alternatively, the self-contained source tarball is at http://www.sagemath.org/download-latest.html As mentioned before, there are no incremental updates from 6.x. You need to compile from scratch, e.g. after

[sage-release] Re: Fix for Sage 6.10 binary for Ubuntu 15.10

Harald, can you replace the file? On the plus side this is fixed for good in Sage-7 by removing (DY)LD_LIBRARY_PATH so we should just get that out of the door. I'll start with sage 7.0.rc0 next... On Tuesday, January 12, 2016 at 4:05:36 PM UTC+1, Eric Gourgoulhon wrote: > > Hi, > > As

[sage-release] Sage 7.0.beta3 released

As always, you can get the latest beta version from the "develop" git branch. Alternatively, the self-contained source tarball is at http://www.sagemath.org/download-latest.html As mentioned before, there are no incremental updates from 6.x. You need to compile from scratch, e.g. after

Re: [sage-release] Sage 7.0.beta2 released

I don't have a sage/local/lib/python2.7/site-packages/flaskext module nor is it on pip; Where is it from? On Tuesday, January 5, 2016 at 4:17:50 PM UTC+1, John Cremona wrote: > > On 5 January 2016 at 09:22, Daniel Krenn <kr...@aon.at > > wrote: > > On 2015-12-30 16:5

[sage-release] Re: Sage 7.0.beta2 released

Looks more like a bug with signals; The preceeding test is too small (or the alarm granularity too large) sage: n = prod(primes_first_n(9)) sage: try: : alarm(1e-5) : _ = n._pari_divisors_small() : except

[sage-release] Re: Sage 7.0.beta2 released

This is now http://trac.sagemath.org/ticket/19816 On Thursday, December 31, 2015 at 8:00:53 PM UTC+1, Volker Braun wrote: > > Looks more like a bug with signals; The preceeding test is too small (or > the alarm granularity too large) > > sage: n = prod(p

[sage-release] Sage 7.0.beta2 released

As always, you can get the latest beta version from the "develop" git branch. Alternatively, the self-contained source tarball is at http://www.sagemath.org/download-latest.html As mentioned before, there are no incremental updates from 6.x. You need to compile from scratch, e.g. after

[sage-release] Re: Sage 7.0.beta1 released

On Wednesday, December 30, 2015 at 1:36:48 AM UTC+1, Andrey Novoseltsev wrote: > > So it is still linked to the build place from which I've copied it. > This is not allowed any more. Build it in the right place, or use https://github.com/sagemath/binary-pkg to build a special relocatable

[sage-release] Re: Sage 7.0.beta1 released

Hmm nDivBy is in libsingular which p_Procs_FieldQ does not link to. Though thats not necessarily wrong. Whats the output of ldd local/bin/p_Procs_FieldQ.so ldd local/lib/libsingular.so sage -singular On Wednesday, December 30, 2015 at 1:05:01 AM UTC+1, Andrey Novoseltsev wrote: > > After

Re: [sage-release] Sage 7.0.beta0 released

I think we should just globally add -L${SAGE_LOCAL}/lib to LDFLAGS, there shouldn't be any reason to prefer system libraries over libraries in Sage -- You received this message because you are subscribed to the Google Groups "sage-release" group. To unsubscribe from this group and stop

Re: [sage-release] Sage 7.0.beta0 released

This is now http://trac.sagemath.org/ticket/19776 On Thursday, December 24, 2015 at 11:20:19 AM UTC+1, Volker Braun wrote: > > I think we should just globally add -L${SAGE_LOCAL}/lib to LDFLAGS, there > shouldn't be any reason to prefer system libraries over libraries in Sage > --

Re: [sage-release] Sage 7.0.beta0 released

The diff you mention is in the configure.ac, so you need to reconfigure (i.e. run SAGE_ROOT/bootstrap) On Wednesday, December 23, 2015 at 11:21:39 AM UTC+1, Sébastien Labbé wrote: > > > > On Wednesday, December 23, 2015 at 11:16:18 AM UTC+1, François wrote: >> >> It looks like one ticket for the

Re: [sage-release] Sage 7.0.beta0 released

So it looks like an ncurses problem: configure:20930: checking for rl_callback_read_char in -lreadline configure:20955: gcc -o conftest -g -O2 -L/home/ncohen/.Sage/local/lib/ -Wl,-rpath,/home/ncohen/.Sage/local/lib -Wl,-rpath,/home/ncohen/.Sage/local/lib64 conftest.c -lreadline >&5

Re: [sage-release] Sage 7.0.beta0 released

R's own config.log, not the Sage config.log... On Wednesday, December 23, 2015 at 6:05:39 PM UTC+1, Nathann Cohen wrote: > > > Can you post the config.log? It does the right thing on my machine: > > SAGE_ROOT/config.log is there: > http://www.steinertriples.fr/ncohen/tmp/config.log > >

Re: [sage-release] Sage 7.0.beta0 released

r: --with-readline=yes (default) and headers/libs > are not available > > I am running "debian testing", with libreadline-dev installed. > > Nathann > > [1] http://www.steinertriples.fr/ncohen/tmp/r-3.2.3.p0.log > > On 23 December 2015 at 12:52, Volker Brau

Re: [sage-release] Sage 7.0.beta0 released

Yours was a different problem. On Wednesday, December 23, 2015 at 11:17:01 PM UTC+1, Emmanuel Charpentier wrote: > > Aha ! > > I *had* problems previously with Sage's libtinfo*, which led bash to spill > a lot of warnings about "missing version information"). The conclusion of > this > thread

[sage-release] Sage 6.10 virtual appliance

The virtual appliance is now at http://files.sagemath.org/win/index.html -- You received this message because you are subscribed to the Google Groups "sage-release" group. To unsubscribe from this group and stop receiving emails from it, send an email to

[sage-release] Sage 7.0.beta0 released

As always, you can get the latest beta version from the "develop" git branch. Alternatively, the self-contained source tarball is at http://www.sagemath.org/download-latest.html As mentioned before, there are no incremental updates from 6.x. You need to compile from scratch, e.g. after

Re: [sage-release] Re: Sage 6.10.rc2 binaries test

The binaries are all built with SAGE_INSTALL_GCC=yes to be as self-contained as possible. AFAIK a default Ubuntu install doesn't include a fortran compiler, for example. The LD_LIBRARY_PATH problem is fixed in Trac #19641 On Tuesday, December 22, 2015 at 9:40:25 AM UTC+1, Eric Gourgoulhon

[sage-release] Re: Sage 6.10 released

The binaries are now on files.sagemath.org Harald: I wrote a script on the buildbot that dumps them into the respective directories on the fileserver. The old binaries still need to be deleted at one point. Maybe you want to let Samuel do that? -- You received this message because you are

Re: [sage-release] Sage 6.10 released

6.10, of course. Does anybody know a way to programmatically post to sage-release? On Friday, December 18, 2015 at 8:26:37 PM UTC+1, HG wrote: > > 6.9 or 6.10 ? > > Le 18/12/2015 20:18, Volker Braun a écrit : > > The "master" git branch has been updated to Sage-6.

Re: [sage-release] Sage 6.10 released

It does! On Friday, December 18, 2015 at 9:04:59 PM UTC+1, Volker Braun wrote: > > Does email actually work? Its not a public group... > > On Friday, December 18, 2015 at 9:01:50 PM UTC+1, Jeroen Demeyer wrote: >> >> On 2015-12-18 20:58, Volker Braun wrote: >

[sage-release] Sage 6.10 released

The "master" git branch has been updated to Sage-6.9. As always, you can get the latest beta version from the "develop" git branch. Alternatively, the self-contained source tarball is at http://www.sagemath.org/download-latest.html a1b60f2 Updated Sage version to 6.10 d9b5c45 Trac #19733:

Re: [sage-release] Sage 6.10 released

Does email actually work? Its not a public group... On Friday, December 18, 2015 at 9:01:50 PM UTC+1, Jeroen Demeyer wrote: > > On 2015-12-18 20:58, Volker Braun wrote: > > Does anybody know a way to programmatically post to sage-release? > https://docs.python.org/2/library/em

[sage-release] Test, please ignore

-- You received this message because you are subscribed to the Google Groups "sage-release" group. To unsubscribe from this group and stop receiving emails from it, send an email to sage-release+unsubscr...@googlegroups.com. To post to this group, send email to sage-release@googlegroups.com.

Re: [sage-release] Sage 6.10 released

Yes, the correct source directory for releases is http://files.sagemath.org/src/index.html On Friday, December 18, 2015 at 10:38:54 PM UTC+1, Justin C. Walker wrote: > > > > On Dec 18, 2015, at 15:18, Volker Braun <vbrau...@gmail.com > > wrote: > > > >

[sage-release] Re: Sage-6.10.rc2 released

Isn't this the non-ascii problem again? /home/riri/Téléchargements On Thursday, December 17, 2015 at 3:46:35 PM UTC+1, HG wrote: > > HI, > I got this problem building rc2 rc1 was ok : > The following package(s) may have failed to build (not necessarily > during this run of 'make all'): > > *

[sage-release] Sage 6.10.rc2 binaries test

Now with the absolute symlinks rewritten to be relative. As before, you can find the tarballs at http://files.sagemath.org/binaries/ -- You received this message because you are subscribed to the Google Groups "sage-release" group. To unsubscribe from this group and stop receiving emails from

[sage-release] Sage-6.10.rc2 released

As always, you can get the latest beta version from the "develop" git branch. Alternatively, the self-contained source tarball is at http://www.sagemath.org/download-latest.html This only fixes a small OSX build issue; The final release is most likely going to be identical to rc2. Please test!

[sage-release] Re: Sage-6.10.rc1 binaries test

The mathjax issue is clear, I'll fix it in the next version (change symlinks to relative) On Wednesday, December 16, 2015 at 8:36:29 AM UTC+1, Samuel Lelievre wrote: > > $ ./sage -n jupyter > From there, I couldn't figure out how to navigate > to my home folder to create a jupyter notebook.

[sage-release] Re: Sage-6.10.rc1 binaries test

Yes. Patches to the documentation are welcome ;-) On Tuesday, December 15, 2015 at 8:53:23 PM UTC+1, kcrisman wrote: > > Yes, use https://github.com/sagemath/binary-pkg >> > Okay. Should we use this rather than `sage -bdist`? > -- You received this message because you are subscribed to the

[sage-release] Sage-6.10.rc1 binaries test

Here is a final test for the binaries, using the new binary packaging. That is, now binaries are patched automatically on first run, no more relocation after that. You can find the following at http://files.sagemath.org/binaries/ sage-6.10.rc1-Debian_GNU_Linux_7-i686.tar.bz2

[sage-release] Re: Sage 6.10.rc0 released

Ticket at http://trac.sagemath.org/ticket/19698 On Sunday, December 13, 2015 at 6:51:02 AM UTC+1, John H Palmieri wrote: > > Building from scratch on OS X 10.11 fails for me. In the singular log: > > error: >

[sage-release] Re: Sage 6.10.rc0 released

On Sunday, December 13, 2015 at 6:51:02 AM UTC+1, John H Palmieri wrote: > > error: > /Applications/Xcode.app/Contents/Developer/Toolchains/XcodeDefault.xctoolchain/usr/bin/install_name_tool: > > changing install names or rpaths can't be redone for: >

[sage-release] Sage-6.10.rc1 released

As always, you can get the latest beta version from the "develop" git branch. Alternatively, the self-contained source tarball is at http://www.sagemath.org/download-latest.html 0a59435 Updated Sage version to 6.10.rc1 b68b4ed Trac #19679: Missing doc dependencies 098b62d Updated Sage version

Re: error building doc still exists in 6.10.rc0 Re: [sage-release] Sage 6.10.beta7 released

On Thursday, December 10, 2015 at 1:00:20 PM UTC+1, Daniel Krenn wrote: > > Still there in 6.10.rc0 when building SageMath: > RuntimeError: In order to initialize the database, > /local/dakrenn/sage/6.10.rc0/local/share/conway_polynomials/conway_polynomials.sobj > > > must exist. > That is

[sage-release] OSX binaries (including El Capitan)

This is a new beta release for the new OSX binaries, available at http://files.sagemath.org/osx/intel/index.html This should now work just like the old binaries; When you start it the first time the paths are automatically patched for the new location, but you do not have to run any special

[sage-release] Sage 6.10.beta7 released

As always, you can get the latest beta version from the "develop" git branch. Alternatively, the self-contained source tarball is at http://www.sagemath.org/download-latest.html 7c27cd2 Updated Sage version to 6.10.beta7 6270d3b Trac #19658: update sympy 0.7.6 -> 0.7.6.1 81a80a8 Trac #19312:

Re: [sage-release] Sage 6.10.beta6 released

One buildbot slave is Haswell-E with gcc 5.1.1 and I can't reproduce it. Though it seems pretty genuine, just increase the tolerance -- You received this message because you are subscribed to the Google Groups "sage-release" group. To unsubscribe from this group and stop receiving emails from

[sage-release] Sage 6.10.beta6 released

As always, you can get the latest beta version from the "develop" git branch. Alternatively, the self-contained source tarball is at http://www.sagemath.org/download-latest.html 8400a23 Updated Sage version to 6.10.beta6 4090066 Trac #19626: OpenSSL hack for El Capitan e17ba67 Trac #19513:

Re: [sage-release] Sage 6.10.beta5 released

On Tuesday, November 24, 2015 at 9:42:31 PM UTC+1, Justin C. Walker wrote: > > This prompts a couple of questions (out of curiosity): > - I trimmed the "--long --warn-long 108.1" part, but sage replaced them, > albeit with a shorter time (105.2). How do it know? And why the > difference? >

[sage-release] Sage 6.10.beta2 released

As always, you can get the latest beta version from the "develop" git branch. Alternatively, the self-contained source tarball is at http://www.sagemath.org/download-latest.html 8a972ca Updated Sage version to 6.10.beta2 38757c2 Trac #19484: sage -unzip d7d1e55 Trac #19459: Fix containment

[sage-release] Sage-6.10.beta0 released

As always, you can get the latest beta version from the "develop" git branch. Alternatively, the self-contained source tarball is at http://www.sagemath.org/download-latest.html Also, a small reminder: Tickets are only being merged after the ticket that they depend on is merged. If your ticket

[sage-release] Sage 6.9 released

The "master" git branch has been updated to Sage-6.9. As always, you can get the latest beta version from the "develop" git branch. Alternatively, the self-contained source tarball is at http://www.sagemath.org/download-latest.html 2cc7f6c Updated Sage version to 6.9 657d6ff Trac #19374: LaTeX

[sage-release] Sage 6.9.rc3 released

As always, you can get the latest beta version from the "develop" git branch. Alternatively, the self-contained source tarball is at http://www.sagemath.org/download-latest.html aabe6d1 Updated Sage version to 6.9.rc3 c504e6e Trac #19338: Doc for deprecated_function_alias() is wrong 277518c

[sage-release] Re: Sage 6.9.rc2 released

whats the output of $ sage -python >>> from notebook.notebookapp import NotebookApp On Monday, October 5, 2015 at 9:07:18 PM UTC+2, Eric Gourgoulhon wrote: > > Hi, > > On Ubuntu 14.04 64bits, the build was OK but when I try > ./sage -n jupyter > I get > > The IPython notebook requires ssl,

[sage-release] Sage 6.9.rc1 released

As always, you can get the latest beta version from the "develop" git branch. Alternatively, the self-contained source tarball is at http://www.sagemath.org/download-latest.html f603730 Updated Sage version to 6.9.rc1 74721d5 Trac #19125: DeprecatedMethod wrapping is broken 1b5a573 Trac #19294:

Re: [sage-release] Re: Sage 6.9.rc0 released

Hmm but /usr/lib/x86_64-linux-gnu/libpari-gmp-tls.so.2.7.2 brings just a slightly different version of Pari's concat. It may very well be that it doesn't trigger libkpathsea crashing but thats just by chance; the symbol conflict is still there. The correct fix is to not export concat; neither

Re: [sage-release] Re: Sage 6.9.rc0 released

Symbol collision. Unless TeX's libkpathsea really intends to use concat() from Pari... -- You received this message because you are subscribed to the Google Groups "sage-release" group. To unsubscribe from this group and stop receiving emails from it, send an email to

Re: [sage-release] Sage 6.9.rc0 released

The wall time isn't comparable, different system load. On Sunday, September 27, 2015 at 3:00:33 PM UTC+2, leif wrote: > > Volker Braun wrote: > > With Sage-6.8 is pretty much the same, maybe ~< 10% less memory usage; > > In any case no drastic change. > > Just a

Re: [sage-release] Sage 6.9.rc0 released

yer wrote: > > On 2015-09-26 14:48, Volker Braun wrote: > > Though afaik our docs say that you need 2gb per process, so you were > > quite a bit below that. It could just be slightly different order of > > execution that blows things up now even though memory consumption didn't

Re: [sage-release] Sage 6.9.rc0 released

Though afaik our docs say that you need 2gb per process, so you were quite a bit below that. It could just be slightly different order of execution that blows things up now even though memory consumption didn't increase. On Saturday, September 26, 2015 at 1:03:49 PM UTC+2, Jeroen Demeyer

Re: [sage-release] Sage 6.9.rc0 released

Graph of CPU + RAM usage of export MAKE='make -j4' make doc -- You received this message because you are subscribed to the Google Groups "sage-release" group. To unsubscribe from this

[sage-release] Sage 6.9.rc0 released

As always, you can get the latest beta version from the "develop" git branch. Alternatively, the self-contained source tarball is at http://www.sagemath.org/download-latest.html This release now supports Xcode 7 but not OSX 10.11. The letter doesn't look encouraging, so I probably won't

[sage-release] Sage 6.9.beta7 released

As always, you can get the latest beta version from the "develop" git branch. Alternatively, the self-contained source tarball is at http://www.sagemath.org/download-latest.html aeeddeb Updated Sage version to 6.9.beta7 a082911 Trac #19182: Allow sage -n jupyter e191893 Trac #18930:

Re: [sage-release] Sage 6.9.beta7 released

Works on the arando buildbot; is it reproducible? On Thursday, September 17, 2015 at 10:00:00 PM UTC+2, Jeroen Demeyer wrote: > > On 2015-09-17 14:07, Volker Braun wrote: > > a7da2fb Trac #14058: Weakly reference binary operation codomains > > On arando: > > sage -t --

[sage-release] Sage 6.9.beta6 released

As always, you can get the latest beta version from the "develop" git branch. Alternatively, the self-contained source tarball is at http://www.sagemath.org/download-latest.html 559f73b Updated Sage version to 6.9.beta6 fc7a4e6 Trac #19067: Incomplete sentences in the automatically generated

Re: [sage-release] Re: Sage 6.9.beta5 released

does a "make distclean && make" fix it? You have both gap-database and gap_database, that can't be good. Probably you are running into one of the many razor-sharp edges of the old+new style packaging mashup. On Tuesday, September 8, 2015 at 4:59:35 PM UTC+2, Anne Schilling wrote: > > > Hi! >

[sage-release] Re: Sage 6.9.beta5 released

Can you delete SAGE_ROOT/upstream/mirror_list, then it should work again On Sunday, September 6, 2015 at 2:44:10 AM UTC+2, kcrisman wrote: > > > > On Saturday, September 5, 2015 at 6:26:02 PM UTC-4, Volker Braun wrote: >> >> The mirror list is not alphabetical so i

[sage-release] Re: Sage 6.9.beta5 released

Works for me now. Harald, is the mirror_list file generated atomically? This looks like it was in the process of being overwritten. On Saturday, September 5, 2015 at 3:12:02 AM UTC+2, kcrisman wrote: > > Upgrading from previous via git pull and make: > > Attempting to download package

[sage-release] Re: Sage 6.9.beta5 released

The mirror list is not alphabetical so its the speed-ranked list. * Whats the snipped part of the log * Does the error persist * Whats the content of SAGE_ROOT/upstream/mirror_list On Saturday, September 5, 2015 at 3:12:02 AM UTC+2, kcrisman wrote: > > Upgrading from previous via git pull and

[sage-release] Re: Sage 6.9.beta3 released

on Debian testing running on Core17+16GB RAM laptop. But the build requires make doc-clean again... HTH, -- Emmanuel Charpentier Le vendredi 21 août 2015 04:16:59 UTC+2, Volker Braun a écrit : As always, you can get the latest beta version from the develop git branch. Alternatively, the self

Re: [sage-release] Re: Sage 6.9.beta3 released

On Friday, August 21, 2015 at 8:28:56 AM UTC-4, Nathann Cohen wrote: Do you think it would make sense to trigger a 'make clean' every time you switch to a new beta? I also do make doc-clean every time I pull a release. make clean only deletes some temp files, so I don't really care. Its

[sage-release] Sage 6.9.beta3 released

As always, you can get the latest beta version from the develop git branch. Alternatively, the self-contained source tarball is at http://www.sagemath.org/download-latest.html 779e5a8 Updated Sage version to 6.9.beta3 89042cb Trac #19004: Do not search old-style spkgs 36ed453 Trac #18712:

[sage-release] Sage 6.9.beta2 released

As always, you can get the latest beta version from the develop git branch. Alternatively, the self-contained source tarball is at http://www.sagemath.org/download-latest.html 314664c Updated Sage version to 6.9.beta2 029ecbb Trac #19022: a few badly formatted REFERENCE block fd064f2 Trac

[sage-release] Re: list of supported platforms

Its a wiki, feel free to edit it. On Wednesday, August 5, 2015 at 10:20:49 AM UTC+2, Samuel Lelievre wrote: Hi sage-release, The list of supported platforms at http://wiki.sagemath.org/SupportedPlatforms needs some tender loving care. In particular, shouldn't the fully supported

[sage-release] Sage-6.9.beta0 released

As always, you can get the latest beta version from the develop git branch. Alternatively, the self-contained source tarball is at http://www.sagemath.org/download-latest.html edb1b08 Updated Sage version to 6.9.beta0 a7cb38e Trac #18962: Double free in ft2font 5b81e36 Trac #16133: delete

Re: [sage-release] Sage 6.8.rc1 released

doctests failed The machine is a rather new HP gen9 server (we have it on loan from HP) may be some code in sympow doesn't like it. Francois On 07/23/15 07:27, Volker Braun wrote: But Scientific Linux is (like Centos) a recompiled Redhat, so we should have that covered

Re: [sage-release] Sage 6.8.rc1 released

But Scientific Linux is (like Centos) a recompiled Redhat, so we should have that covered. On Wednesday, July 22, 2015 at 8:43:24 PM UTC+2, François wrote: Feels unlikely as someone would have suffered from that before you would think. I am suspecting some miscompilation and will force

[sage-release] Sage 6.8.rc1 released

As always, you can get the latest beta version from the develop git branch. Alternatively, the self-contained source tarball is at http://www.sagemath.org/download-latest.html 3648190 Updated Sage version to 6.8.rc1 707189c Trac #18924: Missing dependencies file in package arb 03a4c69 Trac

[sage-release] Re: sagedev error

This might be (accidentally) fixed by #18909, if not please open a ticket... On Friday, July 17, 2015 at 10:16:49 AM UTC+2, Simon King wrote: Hi! With rerere enabled in git (after a suggestion of Volker), I get Failed example: alice.pull() Expected: Merging the remote branch

[sage-release] Re: sagedev error

No, it'll be in rc1 On Friday, July 17, 2015 at 11:14:19 AM UTC+2, Simon King wrote: Hi Volker, On 2015-07-17, Volker Braun vbrau...@gmail.com javascript: wrote: This might be (accidentally) fixed by #18909, if not please open a ticket... Accidentally? The example in the ticket

Re: [sage-release] Sage 6.8.rc0 released

Probably due to #16124... Can you ellipsize the offending strings? On Thursday, July 16, 2015 at 9:42:39 AM UTC+2, Ralf Stephan wrote: make distclean; make; make ptestlong fails on OpenSuSE 13 with sage -t --long src/sage/dev/sagedev.py # 2 doctests failed File src/sage/dev/sagedev.py,

[sage-release] Sage 6.8.beta8 released

As always, you can get the latest beta version from the develop git branch. Alternatively, the self-contained source tarball is at http://www.sagemath.org/download-latest.html 3a13f9f Updated Sage version to 6.8.beta8 92190ca Trac #18873: fix gdb optional test in doctest/test.py 3024420 Trac

<    1   2   3   4   5   6   7   8   9   >