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

On Tue, 25 Jun 2024 at 19:43, John Cremona wrote: > > > On Tue, 25 Jun 2024, 17:44 Antonio Rojas, wrote: > >> gcc -Wno-unused-result -Wsign-compare -DNDEBUG -g -fwrapv -O2 -Wall -g >> -fstack-protector-strong -Wformat -Werror=format-security -g -fwrapv -O2 -g >>

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

x27;re mixing system packages with a locally installed m4ri > Thanks for that suggestion. I do not remember installing that, but I will get rid of it and try again. > El martes, 25 de junio de 2024 a las 17:56:39 UTC+2, John Cremona escribió: > > I failed to build 10.4.rc0 on a ubuntu

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

On Fri, 7 Jun 2024 at 07:33, Dima Pasechnik wrote: > On Thu, Jun 6, 2024 at 2:32 AM John H Palmieri > wrote: > > > > I don't think I've seen this failure before: > > > > sage -t --long --random-seed=214696321465302976857414484526305325295 > src/sage/plot/plot3d/tachyon.py > > ***

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

/logs/pkgs/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 W

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: /usr/local/

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

_on(), sig_off(). 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, Matth

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 > http://ww

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 https://github

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

eeded. Back in about 2007 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'

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

m output" for that >>>> 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? >>>> >>

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 > corre

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 Charpen

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 assume

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: r-SAGE_LOCAL-no

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 opti

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 wo

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 inst

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 --random-seed=133126240

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 2021

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 remem

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'): > > *

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: test_packages(pkgs

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 new l

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 latter

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 merge

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 > src/sag

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 i

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 sage

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 src/sage/game_theory/catalog_normal_f

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 install? >> > > Indeed,

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

On Wed, 16 May 2018, 16:26 Erik Bray, wrote: > On Wed, May 16, 2018 at 9:56 AM, John Cremona > wrote: > > 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 > > > > [scip

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 roots are returned, the func

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.3.beta1 released

On 15 May 2018 at 15:13, Erik Bray wrote: > Thanks for the release. > > On Ubuntu 14.04 I get LOTS of test timeouts that I didn't get > previously. It's possible though that the system is just uder heavy > load, but even re-running the tests with --failed keeps giving me > timeouts for some modu

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

On 13 March 2018 at 09:27, John Cremona wrote: > > > On 13 March 2018 at 09:05, Jeroen Demeyer 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 comp

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

On 13 March 2018 at 09:05, Jeroen Demeyer 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. >> > > Logs please. I shou

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 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. >> >> [dochtml] [manifolds] OSError: [manifol

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 plotting

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 src/sage/schemes/elliptic_curves/heegner.

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 problem. Do you have a custom >

Re: [sage-release] Sage 8.0 released

On 24 July 2017 at 15:21, Jeroen Demeyer wrote: > On 2017-07-24 11:35, John Cremona wrote: >> >> I can attach a log if wanted. > > > Don't ask, just do it automatically. I mean no offense, but an email like > this without log files is almost useless. Yes I know.

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 prev

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 does not have mathematica i

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 apt-get install gcc-fortran >>

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

On 24 January 2017 at 10:02, Jeroen Demeyer 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. >> Should I not have done? >

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

On 24 January 2017 at 09:47, Jeroen Demeyer wrote: (I assume this is in reply to me!) > This is 3 doctest runs concatenated. I will just look at the last one (if > you remember for next time: better just post the log of one run). Sorry, I did not realize that the logs were concatenated. > > Th

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

On 23 January 2017 at 17:04, Jeroen Demeyer wrote: > On 2017-01-23 17:50, John Cremona wrote: >> >> ptestlong.log available on request. > http://homepages.warwick.ac.uk/staff/J.E.Cremona/ptestlong.log.gz > > Yes please. > > > -- > You received this messa

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 sage

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", li

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

.130t in VIRT and only 191692 in RES. I am used to that enormous 0.130t as not signifying anything important (25% of total RAM?). When I start up this new build of 7.5.beta3 it no longer shows that memory message anyway. > > Bill. > > On 19 November 2016 at 13:13, Jeroen Demeyer wrot

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

On 19 November 2016 at 08:18, Jeroen Demeyer 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 PARI failed to allocate the r

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

On 18 November 2016 at 17:25, John Cremona wrote: > Well I just did a make distclean and am rebuilding, so I don't know > how old that log file is -- but the build failure report did point to > that file. I have been inventing or resurrecting old packages, I just > pulled th

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

amuel Lelièvre 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. >> >> The following pack

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: /home/jec/sage/logs/pkgs/python.l

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 >> >> http://homepages.warwick.ac.uk/~masgaj/ftp/database_cremona_ellcurve-20161017.tar.bz2 >> (see https:/

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

I had these failures in 'make ptestlong' after building from source on ubuntu: sage -t --long src/sage/structure/sage_object.pyx # 1 doctest failed sage -t --long src/sage/repl/display/formatter.py # 1 doctest failed sage -t --long src/sage/repl/attach.py # 1 doctest failed sage -t --long src/s

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

essions==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 wrote: >> > On 2015-12-30 16:59, Volker Braun wrote: >> >> As always, you

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 > > make ptestlong w

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

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 wrote: >>> >>

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? Some of the long

Re: [sage-release] Sage 6.9 released

On 17 October 2015 at 08:01, Volker Braun wrote: > The sage pkg-config script uses the system pkg-config if it exists (so you > can use libraries that are installed system-wide), and our own pkgconf > binary if not. The decision is made at Sage build time, so you need to > reinstall (sage -f pkg-c

Re: [sage-release] Sage 6.9 released

penssl_md_meth_names) AttributeError: 'module' object has no attribute 'openssl_md_meth_names' John On 16 October 2015 at 19:57, John Cremona wrote: > Building 6.9 in a directory which had had 6.7, after pulling master > from trac, ./configure and make, I get a failure build

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] 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 wrote: > > > > I also got an error with the brial package (after the same sequence as > kcrisman; the previous beta had built ok): >

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 directory

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

On 16 July 2015 at 14:58, Nathann Cohen 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. > > > and is perhaps

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 "src/sage/graphs/generators/sma

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

On 12 June 2015 at 17:24, Nathann Cohen 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 the latest vers

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

On 12 June 2015 at 14:40, Nathann Cohen 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 can be

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 wrote: > Hello, > >> If I understand correctly, this version (and perhaps some previous ones) >> have fixed the o

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

On 18 May 2015 at 09:59, Harald Schilly 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 option. > > *

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. = CC[] ## line 2189 ## sage: I = ideal([x^2+y^2-1,x*y-1]) ## line 2190 ## sage: I.variety()

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]

t; Ciao, > Thierry > > > On Wed, 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 wrote: >> >> Am 2015-04-0

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 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]

There is "make ssl" -- looking in the Makefile this does "make" and then "./sage -i pyopenssl" which in view of this thread is not sufficient? John On 8 April 2015 at 11:28, Vincent Delecroix <20100.delecr...@gmail.com> wrote: > At least, does 'sage -i openssl' before 'make' work? > > On 08/04/20

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

sly 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 wrote: >> >> Also: >> >> $ locate ft2build.h >> /home/lmfdb/sage1/local/include

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

well as in a system place. On 3 April 2015 at 09:05, John Cremona 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/lm

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

On 3 April 2015 at 09:07, Francois Bissey wrote: > What does PKG_CONFIG_PATH says? That is not set in my bash shell. Should I be looking elsewhere? John > > François >> On 3/04/2015, at 21:05, John Cremona wrote: >> >> I built 6.6.rc2 fine on one machine, but bu

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

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/sage2/local/include/libpng12 -I/home/lmfdb/s age/local/include/freetype2 -g -fvisibility=hidden -M

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 "src/s

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

On 21 March 2015 at 21:40, Emmanuel Charpentier wrote: > Debian testing, core i7, 16 Gb RAM : all tests passed after a parallel > build. Took about 1/ hour starting from beta5. > > FWIW, I still had to "make doc-clean ; make" to finish the build : make > complained that some HTML-related doc didn'

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

On 24 February 2015 at 20:38, Emmanuel Charpentier 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 wrote: >> > On 23 February 2015 at 13:55, Volker Braun wrote: >> >> it is

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

On 23 February 2015 at 14:21, John Cremona wrote: > On 23 February 2015 at 13:55, Volker Braun wrote: >> it is ready ;-) > > OK, testing the build now. With the new git package I rebuilt from scratch and now ptestlong is almost happy. Just some timeouts: sage -t --long src

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

On 23 February 2015 at 13:55, Volker Braun wrote: > it is ready ;-) OK, testing the build now. John > > On Monday, February 23, 2015 at 2:49:53 PM UTC+1, John Cremona wrote: >> >> On 23 February 2015 at 13:47, Volker Braun wrote: >> > I made http://trac.sagemath.

  1   2   >