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

On Wed, 20 Mar 2024 at 12:08, wrote: > On Wed, Mar 20, 2024 at 11:53:49AM +0000, John Cremona wrote: > > Sorry but I have another issue, different machine, also ubuntu 20.04: > > > > The following package(s) may have failed to build (not necessarily > > during

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

/cypari-2.1.4.log Log attached. If it is relevant, I do have a recent pari installed and configure decided it was suitable. John On Wed, 20 Mar 2024 at 11:22, John Cremona wrote: > > > On Wed, 20 Mar 2024 at 10:13, Dima Pasechnik wrote: > >> >> >> On Wed, Mar 20

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

On Wed, 20 Mar 2024 at 10:13, Dima Pasechnik wrote: > > > On Wed, Mar 20, 2024 at 9:53 AM John Cremona > wrote: > >> Thanks for the new release. On a ubuntu machine which I had literally >> only hust upgraded from 20.04 LTS to 22.04.LTS, by build failed here: >

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

Thanks for the new release. On a ubuntu machine which I had literally only hust upgraded from 20.04 LTS to 22.04.LTS, by build failed here: * package: info-6.8 last build time: Mar 20 09:39 log file:/usr/local/sage/sage-10.3/logs/pkgs/info-6.8.log build directory:

Re: [sage-release] Sage 10.2.rc3 released

On Wed, 15 Nov 2023, 17:43 Dima Pasechnik, wrote: > > > On Wed, Nov 15, 2023 at 5:12 PM John Cremona > wrote: > > > > I am seeing failures building from rc3 (commit fa5c9395d3). To make > sure I made a fresh git clone of this and did nothing more than > >

Re: [sage-release] Sage 10.2.rc3 released

). Python will now terminate. Aborted (core dumped) make[6]: *** [Makefile:28: doc-inventory--reference-combinat] Error 134 make[5]: *** [Makefile:45: doc-inventory-reference] Error 2 On Wed, 15 Nov 2023 at 16:05, Matthias Köppe w

Re: [sage-release] Sage 10.2.rc3 released

Is it expected that doing "git pull upstream develop" on top of the rc1 commit should be a merge? On Tue, 14 Nov 2023 at 23:13, Volker Braun wrote: > As always, you can get the latest beta version from the "develop" git > branch. Alternatively, the self-contained source tarball is at >

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

On Mon, 18 Sept 2023 at 09:50, Dima Pasechnik wrote: > run > > make pytest > > (or ./sage -i pytest) > > to install it and have it ready for Sage. > (i.e. install it into Sage's venv) > Thanks Dima John > > On Mon, Sep 18, 2023 at 9:04 AM John Cremona

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

What should I do to avoid this message when running "make testlong": pytest is not installed in the venv, skip checking tests that rely on it i.e. how should I install pytest. System-wide or what? John On Mon, 18 Sept 2023 at 01:08, Matthias Köppe wrote: > I've pushed a fix to

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

7 William and I tried to come up with a deterministic and unique generating set for any elliptic curve but came to conclusion that it was not possible, though we came quite close John > On Friday, June 16, 2023 at 2:57:38 AM UTC-6 John Cremona wrote: > >> I'll review the new PR, though

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

hat >>>> reason, like the other calls of that function have already. >>>> Is this a new pull request or is the old #35626 >>>> https://github.com/sagemath/sage/pull/35626 opened again for >>>> corrections? >>>> >>>> Chris >&

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

On Tue, 13 Jun 2023 at 17:06, John Cremona wrote: > The elliptic curve failure might be a consequence of the recently merged > PR #35626 about using libpari to compute ranks and generators. > > I'll take a look to at least see if the output you get is mathematically > correc

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

The elliptic curve failure might be a consequence of the recently merged PR #35626 about using libpari to compute ranks and generators. I'll take a look to at least see if the output you get is mathematically correct -- generators are not unique. John On Tue, 13 Jun 2023, 17:00 Emmanuel

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

On Mon, 6 Feb 2023 at 15:10, fchap...@gmail.com wrote: > why is the "develop" branch now two commits after the 9.8.rc1 release? > Surely this is bound to happen. Every time a PR is merged, the develop branch's head advances, but there will not be a release (or candidate) every time). I

Re: [sage-release] r-none?

On Fri, 25 Nov 2022 at 14:56, Dima Pasechnik wrote: > > make distclean ? OK, that is always an option. I'll do that. Thanks, John > > On Fri, 25 Nov 2022, 14:40 John Cremona, wrote: >> >> I upgraded from 9.7 after git pull from trac to 9.8.beta4. I did >>

[sage-release] r-none?

I upgraded from 9.7 after git pull from trac to 9.8.beta4. I did ./bootstrap then ./configure then make, and it is complaining about r-none: ... [r-none] [r-none] Error: r is a dummy package and [r-none] cannot be installed using the Sage distribution. make[4]: *** [Makefile:3232:

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

On a machine recently updated to ubuntu 20.04 where I had built 9.7 before, I had to install the package cpre before R would build (I had done bootstrap and configure after make distclean). John On Thu, 6 Oct 2022 at 09:01, Sébastien Labbé wrote: > > On a machine running Ubuntu 20.04 + some

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

I just downloaded sage-9.7.tar.gz from a mirror. Is it deliberate that this tarball contains the entire git repository? (This was also true for 9.6 and 9.5 at least, I think). I would have thought that a release tarball need not contain the git repo stuff, just the files needed to build, which

Re: [sage-release] Re: Sage 9.7.beta8 released

On Sat, 13 Aug 2022, 11:56 Emmanuel Charpentier, < emanuel.charpent...@gmail.com> wrote: > > > Le mercredi 10 août 2022 à 23:01:09 UTC+2, Dima Pasechnik a écrit : > >> On Wed, Aug 10, 2022 at 4:01 PM Emmanuel Charpentier >> wrote: > > > [ Snip... ] > > You tried to feed that "use an editable

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

It looks to me as if this is caused by the recent eclib upgrade. On Sun, 3 Jul 2022, 16:51 Emmanuel Charpentier, < emanuel.charpent...@gmail.com> wrote: > While ptesting an upcoming ticket (irrelevant here), I got two new > permanent errors. The first one is Trac#34029 >

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

I just successfully built 9.5 from a fresh tarball. After completing the build I installed (as I usually do) an optional package with the command-line "./sage -i database_cremona_ellcurve" and now it is rebuilding gmp. What is going on here? Has the way of installing optional packages changed

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

I upgraded from a previous beta and there were no problems with make, just two failures with make ptestlong: sage -t --long --warn-long 133.0 --random-seed=133126240855796926255098246501347092842 src/sage/tests/cmdline.py # 3 doctests failed sage -t --long --warn-long 133.0

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

Upgrading from previous beta with make ptestlong all pass except sage -t --long --warn-long 114.0 --random-seed=0 src/sage/tests/cmdline.py # 3 doctests failed which on rerun shows this: $ ./sage -t --long --warn-long 114.0 --random-seed=0 src/sage/tests/cmdline.py Running doctests with ID

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

On Sat, 4 Jan 2020 at 22:58, Samuel Lelièvre wrote: > Sat 2020-01-04 17:34 UTC, John Cremona: > > > > Apologies now I see that some of the earlier thread on this topic > > was started by me with similar issues (on a different machine). > > I just don't reme

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

On Sat, 4 Jan 2020 at 17:30, John Cremona wrote: > > > On Sat, 4 Jan 2020 at 11:49, John Cremona wrote: > >> Building from source from scratch on ubuntu 16.04 I had a problem: >> >> Error building Sage. >> >> The following package(s) may have failed to

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

On Sat, 4 Jan 2020 at 11:49, John Cremona wrote: > Building from source from scratch on ubuntu 16.04 I had a problem: > > Error building Sage. > > The following package(s) may have failed to build (not necessarily > during this run of 'make all-start'): > > * package:

Re: [sage-release] Sage 9.0.beta10 released

On behalf of all Sage users and deleopers I would like to thank Volker for all his efforts over yet another year as release manager. Your work is much appreciated and I hope you are able to take a break from it for a few days at least! John On Tue, 24 Dec 2019, 15:36 Volker Braun, wrote: > As

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

I had this failure (I have gap_packages installed): sage -t --long --warn-long 59.7 src/sage/tests/gap_packages.py ** File "src/sage/tests/gap_packages.py", line 8, in sage.tests.gap_packages Failed example:

Re: [sage-release] Sage 8.9 released

On Wed, 2 Oct 2019 at 09:07, John Cremona wrote: > > > On Wed, 2 Oct 2019 at 02:22, Dima Pasechnik wrote: > >> something did not work as you installed libncurses5-dev, >> as you still appear to miss >> /usr/include/ncurses.h >> (according to the n

Re: [sage-release] Sage 8.9 released

On Tue, 1 Oct 2019 at 13:42, Dima Pasechnik wrote: > On Tue, Oct 1, 2019 at 7:43 PM John Cremona > wrote: > > > > > > > > On Tue, 1 Oct 2019 at 12:08, Dima Pasechnik wrote: > >> > >> On Tue, Oct 1, 2019 at 6:59 PM Dima Pasechnik > wrote: &g

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

The eclib/interface issue is fixed by #28472 which has a positive review. John On Fri, 13 Sep 2019 at 22:25, Emmanuel Charpentier < emanuel.charpent...@gmail.com> wrote: > On Debian testing running on core i7 + 16 GB RAM, ptestallong gets 12 > transient and 3 permanent faiures (one of the

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

On Thu, 12 Sep 2019 at 20:30, Dima Pasechnik wrote: > On Thu, Sep 12, 2019 at 5:55 PM John Cremona > wrote: > > > > On ubuntu, upgrade from previous beta, python3 configured: make > ptestlong succeeds except for > > > > sage -t --long --warn-long 81.2 src

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

On ubuntu, upgrade from previous beta, python3 configured: make ptestlong succeeds except for sage -t --long --warn-long 81.2 src/sage/libs/gap/element.pyx # 147 doctests failed John On Thu, 12 Sep 2019 at 12:13, 'Justin C. Walker' via sage-release < sage-release@googlegroups.com> wrote: > >

Re: [sage-release] Sage 8.9.beta8 released

#28372 is an easy one On Sun, 25 Aug 2019, 23:37 Volker Braun, wrote: > 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 > > It is nearing the end of the 8.9

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

On Tue, 2 Apr 2019 at 09:05, Emmanuel Charpentier < emanuel.charpent...@gmail.com> wrote: > On a smaller machine (core i5+8GB RAM, Denian testing), I get one > transient failure : > > -- > sage -t --long --warn-long 50.2 >

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

On Thu, 3 Jan 2019 at 17:23, John Cremona wrote: > I am failing to build 8.5 on one machine. I had a working build of 8.4, > built from source from a git clone, and used git pull to update (to > commit 934b744f65) from trac/master. After the first fail I did "make > distclea

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

I am failing to build 8.5 on one machine. I had a working build of 8.4, built from source from a git clone, and used git pull to update (to commit 934b744f65) from trac/master. After the first fail I did "make distclean" before another make. The failing package is cypari-1.3.1 and the log file

Re: [sage-release] Sage 8.3 released

I built 8.3 on about 8 machines running ubuntu 14.04 or 16.04 with no problems. In each case I did "make distclean" first; I was building on top of 8.1. Running ptestlong on two of the machines resulted in sage -t --long src/sage/game_theory/catalog_normal_form_games.py # 15 doctests failed

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

Built 8.3.beta1 from scratch (after make distclean at least after previously reported pip version issues). Two failing files both complaining that lrslib is not found: sage -t --long src/sage/game_theory/normal_form_game.py # 2 doctests failed sage -t --long

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

On 16 May 2018 at 22:15, Jeroen Demeyer wrote: > On 2018-05-16 17:26, Erik Bray wrote: > >> I'm not sure, but I think this might be pip-related. I think Jeroen >> mentioned something about this to me a couple weeks ago. Is it >> possible you upgraded the pip in your Sage

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

On 16 May 2018 at 12:06, Samuel Lelièvre wrote: > Would changing the doctest from > > sage: pol.roots(multiplicities=False, proof=False) > > to > > sage: sorted(pol.roots(multiplicities=False, proof=False)) > > solve this? > I think that in other places where

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

I started to build this yesterday after pulling from trac into a place where beta0 had already built OK. This morning I find the lines [scipy-0.19.1] Skipping scipy as it is not installed. [scipy-0.19.1] Skipping scipy as it is not installed. [scipy-0.19.1] Skipping scipy as it is not installed.

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

On 13 March 2018 at 09:27, John Cremona <john.crem...@gmail.com> wrote: > > > On 13 March 2018 at 09:05, Jeroen Demeyer <j.deme...@ugent.be> wrote: > >> On 2018-03-13 10:02, John Cremona wrote: >> >>> I had a couple of failures on a ubuntu machi

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

On 13 March 2018 at 09:05, Jeroen Demeyer <j.deme...@ugent.be> wrote: > On 2018-03-13 10:02, John Cremona wrote: > >> I had a couple of failures on a ubuntu machine where the previous beta >> was fine, both complaining about permissions of files in /tmp. >> > >

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

I had a couple of failures on a ubuntu machine where the previous beta was fine, both complaining about permissions of files in /tmp. When I looked I saw that files with the same names existed in there owned by sage-patchbot (which is running on the same machine). These are the ones: -rw-rw-r--

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

I installed clang on my ubuntu laptop. I use synaptic ( a front-end for apt & co) for installing stuff as it's easier to search. There's a package "clang" and I have clang-3.8 installed as well as libclang-common-3.8-dev (and there are others like tthat with 3.8 replaced by other versions), also

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

On 18 November 2017 at 16:47, Eric Gourgoulhon <egourgoul...@gmail.com> wrote: > > > Le samedi 18 novembre 2017 14:46:14 UTC+1, John Cremona a écrit : >> >> Does anyone know what this is about? Building 8.1.rc1 after make >> distclean. >> >> [doch

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

Does anyone know what this is about? Building 8.1.rc1 after make distclean. [dochtml] [manifolds] OSError: [manifolds] WARNING: /home/jec/sage/local/lib/python2.7/site-packages/sage/manifolds/chart.py:docstring of sage.manifolds.chart.RealChart.plot:104: (WARNING/2) Exception occurred in

Re: [sage-release] Sage 8.1.beta8 released

On 20 October 2017 at 08:00, Vincent Delecroix <20100.delecr...@gmail.com> wrote: > On a freshly compiled Sage on the quasar patchbot I got two doctet failures > in respectively schemes/elliptic_curves/heegner.py and interfaces/qepcad.py. > > sage -t --long

Re: [sage-release] Sage 8.1.beta4 released

On 6 September 2017 at 11:11, Jeroen Demeyer wrote: > On 2017-09-06 01:55, Vincent Delecroix wrote: >> >> sage -t --long --warn-long 74.4 >> src/sage/schemes/elliptic_curves/ell_number_field.py # 18 doctests failed > > > It seems that you are the only one with this

Re: [sage-release] Sage 8.0 released

On a ubunti machine where I had 7.5 installed I did a simple "make" after "git pull origin master" where origin = trac and it failed to build cython saying "Unable to find pgen, not compiling formal grammar." I can attach a log if wanted. I often make a release based on the one two releases

Re: [sage-release] Re: Sage 8.0.beta8 released

On 31 May 2017 at 10:43, Jeroen Demeyer wrote: > On 2017-05-30 23:51, John H Palmieri wrote: >> >> I'm getting intermittent timeouts from src/sage/doctest/external.py, and >> in particular the "has_mathematica()" test. This is a new (but >> underpowered) computer and it

Re: [sage-release] Re: Why is gcc built?

On 22 February 2017 at 16:08, Simon King wrote: > > > Am Mittwoch, 22. Februar 2017 17:04:48 UTC+1 schrieb Jeroen Demeyer: >> >> On 2017-02-22 16:50, Simon King wrote: >> > So, it seems that the problem lies in Fortran compiler, right? But I did >> > do >> >sudo

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

On 24 January 2017 at 10:02, Jeroen Demeyer <jdeme...@cage.ugent.be> wrote: > On 2017-01-24 10:54, John Cremona wrote: >> >> Quite possibly. If I use pip to install something and it tells me >> that my pip os out of date I usually obey instructions and update it

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

+1 for the fact that "git pull trac develop; make" completed without the usual "make doc-clean", but -1 for: sage -t --long src/sage/doctest/test.py # 16 doctests failed sage -t --long src/sage/tests/cmdline.py # 2 doctests failed sage -t --long src/sage/misc/package.py # 9 doctests failed

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

On 20 December 2016 at 09:38, Vincent Delecroix <20100.delecr...@gmail.com> wrote: > Hello, > > Beyond the doctest failures related to giacpy and cbc already reported I got > this one > > ** > File "src/sage/databases/jones.py",

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

t 13:13, Jeroen Demeyer <jdeme...@cage.ugent.be> wrote: >> >> On 2016-11-19 10:27, John Cremona wrote: >>> >>> It seems strange to me that pari would need to allocate an >>> enormous amount of memory as Sage starts up. >> >> >> Maybe strange

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

On 19 November 2016 at 08:18, Jeroen Demeyer <jdeme...@cage.ugent.be> wrote: > On 2016-11-18 20:58, John Cremona wrote: >> >>*** Warning: not enough memory, new stack 69618196480 >> >> -- what's that about (the last line)? > > > It means that PA

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

Lelièvre <samuel.lelie...@gmail.com> wrote: > > > 2016-11-18 10:06 GMT+01:00 John Cremona: > >> Build failure on ubuntu, based on a successful build of the previous >> beta and following "git pull trac develop": >> >> Error building Sage. >

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

Build failure on ubuntu, based on a successful build of the previous beta and following "git pull trac develop": Error building Sage. The following package(s) may have failed to build (not necessarily during this run of 'make all'): * package: python log file:

Re: [sage-release] Re: database_cremona_ellcurve-20161017 is not mirrored

On 2 November 2016 at 17:45, Volker Braun wrote: > ok, done. > Thanks, Jeroen and Volker! > > On Wednesday, November 2, 2016 at 10:22:26 PM UTC+1, Jeroen Demeyer wrote: >> >> Please mirror >> >>

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

-OldSessions==0.10 Flask-OpenID==1.2.5 Flask-Silk==0.2 John > > > 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:59, Volker Braun wrote: >>

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

On 5 January 2016 at 09:22, Daniel Krenn wrote: > On 2015-12-30 16:59, Volker Braun wrote: >> 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 > >

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

On 13 November 2015 at 00:29, Rob Beezer wrote: > On SageMathCloud, built from source, passes long tests ("ptestlong"), except > > src/sage/schemes/elliptic_curves/ell_number_field.py > > timed out first time, and passed when run independently. Can you say which test timed out?

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

al model of each curve in the isogeny class, and it is that step which takes a long time over a large degree field. Sorry. John > HTH, > Rob > > > > > On 11/17/2015 06:13 AM, John Cremona wrote: >> >> On 13 November 2015 at 00:29, Rob Beezer <bee...@ups.e

Re: [sage-release] Sage 6.9 released

Building 6.9 in a directory which had had 6.7, after pulling master from trac, ./configure and make, I get a failure building brial: checking for pkg-config... /usr/local/sage/sage-1/local/bin/pkg-config checking pkg-config is at least version 0.9.0... /usr/local/sage/sage-1/local/bin/pkg-config:

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

I also got an error with the brial package (after the same sequence as kcrisman; the previous beta had built ok): While running its configure script I get checking pkg-config is at least version 0.9.0... /home/jec/sage/local/bin/pkg-config: line 16: /usr/bin/pkg-conf ig: No such file or

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

fter installing pkg-config on the system (ubuntu 14.04) it builds ok. John > > François > > > On 5/09/2015, at 23:04, John Cremona <john.crem...@gmail.com> wrote: > > > > I also got an error with the brial package (after the same sequence as > kcrisman; the pre

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

On Ubuntu 14.04, make ptestlong has 3 problems: sage -t --long src/sage/combinat/sf/sfa.py # Bad exit: 2 sage -t --long src/sage/graphs/generators/smallgraphs.py # 1 doctest failed sage -t --long src/sage/sandpiles/sandpile.py # Timed out The second one is File

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

On 16 July 2015 at 14:58, Nathann Cohen nathann.co...@gmail.com wrote: sage -t --long src/sage/graphs/generators/smallgraphs.py # 1 doctest failed This one is my fault. It has been fixed there: http://trac.sagemath.org/ticket/18911 Nice to see the happy cooperation on that ticket.

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

On 12 June 2015 at 17:24, Nathann Cohen nathann.co...@gmail.com wrote: No, that version really is installed. I know that because (1) $ cat build/pkgs/database_cremona_ellcurve/package-version.txt 20150519 I was trying to convince you that this, in particular, does *not* mean that you have

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

On 12 June 2015 at 14:40, Nathann Cohen nathann.co...@gmail.com wrote: Another wrong output is database_cremona_ellcurve... 20121022 (20140829) where the version actually installed is 20150519 ! That's surprising. Could you confuse version installed with the latest version that

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

Another wrong output is database_cremona_ellcurve... 20121022 (20140829) where the version actually installed is 20150519 ! John On 12 June 2015 at 14:28, Nathann Cohen nathann.co...@gmail.com wrote: Hello, If I understand correctly, this version (and perhaps some previous ones)

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

On 18 May 2015 at 09:59, Harald Schilly harald.schi...@gmail.com wrote: On Monday, May 18, 2015 at 1:28:45 AM UTC+2, Volker Braun wrote: The self-contained binary tarball is on its way to the mirrors. This is a short promotion to use the torrent file. Personally, I think this is the best

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

6.7.rc0: all tests passed (ptestlong) except sage -t --long src/sage/rings/polynomial/multi_polynomial_ideal.py # Timed out -- the machine was not under any load. Rerunningtimes out again: sage: R.x,y = CC[] ## line 2189 ## sage: I = ideal([x^2+y^2-1,x*y-1]) ## line 2190 ## sage:

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

Testing 6.7.beta1 after building from source. Running make testlong, it has been on sage -t --long src/sage/schemes/elliptic_curves/lseries_ell.py for a while. But the underlying gp process has been running for 17 minutes and is using 0.108tb (terabytes!) of RAM, so I had to kill it as it was

Re: Install with openssl [Re: [sage-release] Re: Sage 6.6.rc2 released]

On 8 April 2015 at 11:53, Vincent Delecroix 20100.delecr...@gmail.com wrote: On 08/04/2015, Daniel Krenn kr...@aon.at wrote: Am 2015-04-08 um 12:28 schrieb Vincent Delecroix: At least, does 'sage -i openssl' before 'make' work? Seems to be possible (tried; but still compiling). If it does,

Re: Install with openssl [Re: [sage-release] Re: Sage 6.6.rc2 released]

, Apr 08, 2015 at 12:01:35PM +0100, John Cremona wrote: On 8 April 2015 at 11:53, Vincent Delecroix 20100.delecr...@gmail.com wrote: On 08/04/2015, Daniel Krenn kr...@aon.at wrote: Am 2015-04-08 um 12:28 schrieb Vincent Delecroix: At least, does 'sage -i openssl' before 'make' work? Seems

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

installed version. Notice “sage” instead of “sage2”. I would have to dig the list to find what it was last time. François On 3/04/2015, at 21:17, John Cremona john.crem...@gmail.com wrote: Also: $ locate ft2build.h /home/lmfdb/sage1/local/include/freetype2/ft2build.h /home/lmfdb/sage2/local

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

as well as in a system place. On 3 April 2015 at 09:05, John Cremona john.crem...@gmail.com wrote: I built 6.6.rc2 fine on one machine, but building it again on the same machine (different directory) I had an error building libgd: libtool: compile: gcc -std=gnu99 -DHAVE_CONFIG_H -I. -I/home/lmfdb

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

I finally got around to building 6.5 on my small netbook, running ubuntu-14.04. Among the doctest failures, most of which are just timeouts (slow machine) there are things like this: sage -t --long src/sage/all.py ** File

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

On 24 February 2015 at 20:38, Emmanuel Charpentier emanuel.charpent...@gmail.com wrote: Le mardi 24 février 2015 10:52:23 UTC+1, John Cremona a écrit : On 23 February 2015 at 14:21, John Cremona john.c...@gmail.com wrote: On 23 February 2015 at 13:55, Volker Braun vbrau...@gmail.com wrote

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

stuck at 1.9.1. John On Monday, February 23, 2015 at 2:16:17 PM UTC+1, leif wrote: On 02/23/2015 01:51 PM, Samuel Lelievre wrote: 2015-02-23 10:40:06 UTC+1, Dima Pasechnik: On 2015-02-23, John Cremona john.c...@gmail.com javascript: wrote: On 22 February 2015 at 22:27, Volker

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

git package is 1:1.9.1-1ubuntu0.1. As for Emmanuel, I built this in parallel. I will try make distclean and a non-parallel build and report back (but not for a while!) John On Sunday, February 22, 2015 at 10:34:27 PM UTC+1, John Cremona wrote: I upgraded and buiult OK on ubuntu 14.04

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

It's a long time since I have done a make ptestlong and not had several test failures. I have done make distclean first and have pulled the latest develop branch (commit 8b95db32005c62e289d6698e8233218d5fda0f60) but see this: sage -t --long src/sage/matrix/matrix_double_dense.pyx # 1 doctest

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

On 4 November 2014 13:56, Volker Braun vbraun.n...@gmail.com wrote: At least the ones you mention are in #17278 which will be in rc2 Good! looking forward to it. John On Tuesday, November 4, 2014 1:16:43 PM UTC, John Cremona wrote: It's a long time since I have done a make ptestlong

Re: [sage-release] Sage 6.4.beta4 released

On 28 September 2014 17:47, John Cremona john.crem...@gmail.com wrote: I am getting a doctest failure in src/doc/en/bordeaux_2008/elliptic_curves.rst and I wonder if others can confirm or deny. You should have sage: C = CremonaDatabase() sage: C[37] {'allcurves': {'a1': [[0, 0, 1, -1, 0], 1

Re: [sage-release] Sage 6.4.beta4 released

On 27 September 2014 16:32, Harald Schilly harald.schi...@gmail.com wrote: On Sat, Sep 27, 2014 at 4:51 PM, Volker Braun vbraun.n...@gmail.com wrote: Note: boxen will be reinstalled soon, and the source tarball link might be unavailable. Watch this thread for an updated url ;-) should one of

Re: [sage-release] Sage 6.4.beta4 released

, John Cremona wrote: On 27 September 2014 16:32, Harald Schilly harald@gmail.com wrote: On Sat, Sep 27, 2014 at 4:51 PM, Volker Braun vbrau...@gmail.com wrote: Note: boxen will be reinstalled soon, and the source tarball link might be unavailable. Watch this thread for an updated

Re: [sage-release] Sage 6.3 released

On 12 August 2014 10:29, Nathann Cohen nathann.co...@gmail.com wrote: Hell ! - Nathann Cohen [first contribution] - Nathann Cohen [? New incarnation?] I don't mind reincarnating, but I would prefer it to happen *after* I die. Just think about how much more work you could get

Re: [sage-release] Sage 6.3 released

On 12 August 2014 10:34, leif not.rea...@online.de wrote: On 12.08.2014 11:29, Nathann Cohen wrote: Hell ! - Nathann Cohen [first contribution] - Nathann Cohen [? New incarnation?] I don't mind reincarnating, but I would prefer it to happen *after* I die. Well,

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

I have these failures with make ptestlong (ubuntu 12.04): sage -t --long src/sage/plot/plot.py # 20 doctests failed sage -t --long src/sage/gsl/probability_distribution.pyx # 4 doctests failed sage -t --long src/sage/sandpiles/sandpile.py # Timed out The plot and gsl ones are all caused by

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

unhelpful noise caused by some settings of the distro. What's more I don't get that one in sage-on-gentoo probably because I build matplotlib with different options. François On 30/07/2014, at 21:36, John Cremona john.crem...@gmail.com wrote: I have these failures with make ptestlong (ubuntu

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

but the test still gives the error about failing to connect to localhost:12.0 John François On 30/07/2014, at 22:21, John Cremona john.crem...@gmail.com wrote: On 30 July 2014 11:10, Francois Bissey francois.bis...@canterbury.ac.nz wrote: Not exactly. The problem here is that some component

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

On 9 June 2014 23:55, Volker Braun vbraun.n...@gmail.com wrote: Thanks for the investigative work! Using the terminal echo isn't really a solution, maybe it doesn't fail as often but it cannot work all the time. The terminal echo can and will occasionally (rarely) be interleaved with the

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

On 10 June 2014 09:53, leif not.rea...@online.de wrote: John Cremona wrote: On 9 June 2014 23:55, Volker Braun vbraun.n...@gmail.com wrote: Thanks for the investigative work! Using the terminal echo isn't really a solution, maybe it doesn't fail as often but it cannot work all the time

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

On 14 May 2014 01:46, Justin C. Walker jus...@mac.com wrote: On May 13, 2014, at 08:34 , Volker Braun wrote: Get it from the updated develop git branch or the source tarball at http://boxen.math.washington.edu/home/release/sage-6.3.beta1.tar.gz Built 6.3-beta1 (both 10.6.8, Dual 6-core

[sage-release] 6.2.beta8 problem

This is a different problem to the one I reported on the other sage-release thread. On my laptop (ubuntu 12.04) I had a working build of a previous beta, I think beta6. I pulled from trac/develop and ran a make. Here's the error message: [ -f local/etc/sage-started.txt ] ||

Re: [sage-release] Sage 6.2.beta8 released

. Doing that much the same. 4 subprocesses are running, it got to exactly the same point, one of the four is using 99% CPU but doing nothing that strace notices. And if I kill that process I get more activity logged until it stops again. John François On 16/04/2014, at 23:43, John Cremona

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

On 2 April 2014 10:00, Maarten Derickx m.derickx.stud...@gmail.com wrote: I really like the new git based workflow. It makes it much faster to update my dev version of sage, however this update failed. Using OS X 10.9.2 I get: DId you do make before sage -b? You should. John lll:sage

  1   2   >