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

e-antic is indeed not compatible (yet) with flint-3.0.0, see https://github.com/flatsurf/e-antic/issues/263 On Tue, 12 Dec 2023 at 08:32, 'tsc...@ucdavis.edu' via sage-release wrote: > > I am having an issue building e_antic that was not present for building 10.2 > from source. I've included

Re: [sage-release] A detail that matters - please help

I agree with Marc that svg is almost always preferable than png for graphics : it scales and compresses. Thanks for raising the issue. Do you have a concrete proposal for making the change png -> svg happen? I guess there is a lot of files that would be involved in the transition. Vincent On

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

Most likely Trac #33876: Make ModularFormsRing.gen_forms returns GradedModularFormElement object On Sun, 19 Jun 2022 at 22:05, G. M.-S. wrote: > > > Thanks, Volker. > > This is on Apple Silicon Macs with Homebrew up to date and make pytest. > > On macOS 11.6.7 (Big Sur) with Xcode 13.2.1 and

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

Got a matplotlib related doctest failure in graph plotting (via elliptic curves on this example) File "ell_number_field.py", line 2752, in sage.schemes.elliptic_curves.ell_number_field.EllipticCurve_number_field.isogeny_class Failed example: G.show(edge_labels=True) # long time Exception

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

Got a matplotlib related doctest failure in graph plotting (via elliptic curves on this example) File "ell_number_field.py", line 2752, in sage.schemes.elliptic_curves.ell_number_field.EllipticCurve_number_field.isogeny_class Failed example: G.show(edge_labels=True) # long time Exception

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

I got two doctest failures on a freshly compiled sage on Debian bullseye (see below). The first one looks similar to https://trac.sagemath.org/ticket/27477. The second one is plausibly dependent on the version of gmp used. Best Vincent sage -t --long --warn-long 40.6

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

Maybe it is time to upgrade to fpylll-0.5.4 (Sage is stuck at 0.5.2dev), see ticket [#31025]. [#31025] https://trac.sagemath.org/ticket/31025 Vincent Le 15/12/2020 à 13:07, Vincent Delecroix a écrit : fpyll does not build (error in the C compilation). Log attached. Best Vincent Le 15/12

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

My documentation failed to build (compiled from scratch) [dochtml] [combinat ] The inventory files are in local/share/doc/sage/inventory/en/reference/combinat. [dochtml] Error building the documentation. [dochtml] Traceback (most recent call last): [dochtml] File

Re: [sage-release] Re: Sage 9.2.beta12 released

Le 16/09/2020 à 11:51, Eric Gourgoulhon a écrit : Side note: the launch of Sage in a terminal is very fast on this computer, less then 2 seconds. Maybe this is due to the use of the system Python? On my computer, I have 3 sage with the following startup times * conda (Sage 9.1, Python 3.7.8):

Re: [sage-release] Re: Sage 9.1.beta9 released

Le 29/03/2020 à 21:50, Matthias Köppe a écrit : Let me remark that this is the first beta that tries to use the system python3 in a venv (#27824) instead of building our own copy of python3. Tests of building from scratch or (after "make python3-clean") would be valuable. Very

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

Le 26/08/2019 à 12:06, Eric Gourgoulhon a écrit : Le lundi 26 août 2019 00:37:50 UTC+2, Volker Braun a écrit : I'm inclined to name the next version 9.0. In particular, we now have Python 3 support that, while not perfect, is at least usable so we should mark that with a new major version.

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

Apparently libsemigroups (ticket 27396) is not on the mirrors. Le 10/08/2019 à 19:49, Volker Braun a écrit : 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] Re: Sage 8.9.beta2 released

Le 10/07/2019 à 18:08, Emmanuel Charpentier a écrit : sage -t --long --warn-long 53.1 src/sage/geometry/polyhedron/combinatorial_polyhedron/base.pyx # 1 doctest This is https://trac.sagemath.org/ticket/28153 -- You received this message because you are subscribed to the Google Groups

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

From the log Error: No module named 'Cython' The installation of ppl requires Cython Cython is a build dependency of pplpy. This is not specified in dependencies.txt and might be the origin of the trouble. Though it looks suspicious since it depends on cysignals that depends itself

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

+1 Some users reported that they prefer reading pdf rather than html. Le 26/06/2019 à 22:59, François Bissey a écrit : Print no. But I have users of sage-on-gentoo who have told me that they find it handy and consult it from their phone and stuff. On 27/06/2019, at 5:03 AM, Volker Braun

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

Could you check whether there is a config.log in /home/slabbe/GitBox/sage/local/var/tmp/sage/build/pynormaliz-2.5 and if so attach it. Vincent Le 23/05/2019 à 10:25, Sébastien Labbé a écrit : My first try at installing finishes with an error installing the (optional?) package pynormaliz

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

I can not reproduce the error. What is the configuration of your machine? The comparison routine in QQbar that is called (cmp_elements_with_same_minpoly) assumes that the elements a and b have the same minimal polynomial p. But the error message is weird as it does not seem to be the case. The

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

I do have a valid tarball on my computer $ sha1sum cryptominisat-5.6.6.tar.gz 568cd2f528609a31d217e24e381de87e011499d4 And I confirm that the one downloaded from mirrorservice.org is broken $ sha1sum cryptominisat-5.6.6.tar.gz 0ff5ce55d8e3d199c81c5ebef5abf7f06a47796a It is a completely broken

Re: [sage-release] Sage 8.3 released

On 03/08/2018 03:47, Volker Braun wrote: The "master" git branch has been updated to Sage-8.3. 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 There was no change

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

See https://trac.sagemath.org/ticket/25399 On 21/05/2018 05:25, François Bissey wrote: If the optional package bliss is installed the following doctests fail: sage -t --long --warn-long 83.4 src/sage/geometry/polyhedron/base.py  # 4 doctests failed sage -t --long --warn-long 83.4

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

On 15/05/2018 21:24, Sébastien Labbé wrote: On Ubuntu 16.04, the command `./sage -t -p --all --long --optional=sage,optional,external` finishes with: sage -t --long src/sage/coding/code_constructions.py ** File

Re: [sage-release] Re: Release process

On 16/05/2018 10:57, Jeroen Demeyer wrote: On 2018-05-16 10:30, Vincent Delecroix wrote: And I agree: there should be two branches whatever they are called. Let's go for "develop + integration" (that were "integration" + "TMP" in my previous e-mail). In that

Re: [sage-release] Re: Release process

On 16/05/2018 10:26, Jeroen Demeyer wrote: On 2018-05-16 10:23, Vincent Delecroix wrote: TMP is public! People should just not base their work on as it is likely to be abandoned. On the other hand, people should be encouraged to base their work on "integration" and not on &q

Re: [sage-release] Re: Release process

On 16/05/2018 10:15, Jeroen Demeyer wrote: On 2018-05-16 10:06, Vincent Delecroix wrote: On 15/05/2018 17:07, Volker Braun wrote: The integration branch is going to have its history rewritten regularly. Why is that? Shouldn't the process be simply    1. create a branch TMP = "integr

Re: [sage-release] Re: Release process

On 15/05/2018 17:07, Volker Braun wrote: The integration branch is going to have its history rewritten regularly. Why is that? Shouldn't the process be simply 1. create a branch TMP = "integration branch" + "merged positive review ticket" 2. if merge fails: move back ticket to needs work

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

If it is, it is not the only one, see https://trac.sagemath.org/ticket/25332 Vincent On 10/05/2018 10:21, François Bissey wrote: It is probably an oversight or a corner case in https://trac.sagemath.org/ticket/20382 Do open a ticket for that. François On 10/05/2018, at 20:15, Emmanuel

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

Congratulations Erik! You found the field with one element in SageMath: https://en.wikipedia.org/wiki/Field_with_one_element I am really impressed. Vincent On 14/03/2018 16:49, Erik Bray wrote: I am now pretty consistently getting the following failure on Cygwin with 8.2beta8 (although

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

Sage 8.2.beta8 is badly breaking the optional package meataxe. See https://trac.sagemath.org/ticket/24947 Vincent -- 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

[sage-release] Re: Sage 8.2.beta3 released (R build failure)

[#24575] https://trac.sagemath.org/ticket/24575 On 18/01/2018 10:44, Vincent Delecroix wrote: I restart a build from scratch and I don't believe that R is responsible in any way. This new build stopped on flint pointing at the same library issue make: symbol lookup error: /usr/lib/libguile-2.2.so.1

[sage-release] Re: Sage 8.2.beta3 released (R build failure)

On 18/01/2018 10:05, Vincent Delecroix wrote: On archlinux (gcc 7.2.1) I failed to build the R new package with the recent upgrade to 8.2.beta3. See log attached. On 18/01/2018 01:01, Volker Braun wrote: After reinstalling the OSX buildslave from scratch since the OSX 10.13 upgrade resulted

[sage-release] matrix/special.py failure on Sage 8.2.beta1

Hello, On sage-8.2.beta1, several patchbots report failures in matrix/special.py. I opened https://trac.sagemath.org/ticket/24449 Vincent -- You received this message because you are subscribed to the Google Groups "sage-release" group. To unsubscribe from this group and stop receiving

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

Also reported a year ago https://groups.google.com/forum/#!topic/sage-devel/deDNSst_dRY On 30/12/2017 07:11, Dima Pasechnik wrote: I am getting a segfault in sage/matrix/matrix_integer_dense.pyx namely, at line 222. This also crashes at the console: sage: Matrix(ZZ, sys.maxsize, sys.maxsize)

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

On 06/09/2017 05: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 version of some

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

sage -t --long --warn-long 74.4 src/sage/schemes/elliptic_curves/ell_number_field.py # 18 doctests failed (see attached log) On 05/09/2017 18:50, Justin C. Walker wrote: On Sep 5, 2017, at 11:37 , Volker Braun wrote: As always, you can get the latest beta version

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

On 22/06/2017 22:11, Volker Braun wrote This might be the last beta for 8.0, so if you have anything super urgent let me know... If we are about to switch to Jupyter as a default, then I guess that https://trac.sagemath.org/ticket/22777 would better be fixed. -- You received this message

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

Henri, can you post the log SAGE_ROOT/logs/pkgs/ singular-4.1.0p1.log? How should we guess why your build failed without any information? It might be due to 96400c9 Trac #22606: singular build option --disable-polymake Vincent On 31/03/2017 08:19, Henri Girard wrote: Hi, ubuntu 16.04 ,

Re: [sage-release] Sage 7.6 released

Thanks Volker. I was about to update trac for the new milestone. The next release is intended to be 7.7 or 8.0? On 25/03/2017 16:11, Volker Braun wrote: The "master" git branch has been updated to Sage-7.6. As always, you can get the latest beta version from the "develop" git branch.

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

On 13/02/2017 14:32, Sébastien Labbé wrote: On Ubuntu 16.06, make ptestlong with MAKE="make j6" had one failing test which I can not reproduce: sage -t --long --warn-long 36.7 src/sage/homology/simplicial_complex.py ** File

Re: [sage-release] Re: Conda package for Sage

Le 05/02/2017 à 21:13, Samuel Lelievre a écrit : Sun 2017-02-05 13:27:02 UTC+1, Isuru Fernando: I've packaged sage 7.5.1 for conda for linux and have uploaded it to anaconda.org. To try it out you can do on linux with miniconda3, (Downloads about 1 GB) conda create -n sage sage

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

Hello, Beyond the doctest failures related to giacpy and cbc already reported I got this one ** File "src/sage/databases/jones.py", line 255, in sage.databases.jones.JonesDatabase.ramified_at Failed example:

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

Some optional doctests fail (probably due to #20946). sage -t --long src/sage/rings/polynomial/multi_polynomial_ideal.py ** File "src/sage/rings/polynomial/multi_polynomial_ideal.py", line 3532, in

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

I created #21402. On 02/09/16 12:38, Johan S. H. Rosenkilde wrote: I got the following doctest failure (with gap_packages installed) These are because of #21165, which was apparently not well enough tested. And two other errors in "src/sage/coding/databases.py" These are weird though,

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

I got the following doctest failure (with gap_packages installed) ** File "src/sage/coding/linear_code.py", line 3059, in sage.coding.linear_code.AbstractLinearCode.weight_distribution Failed example:

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

#21357 needs review On 27/08/16 22:02, leif wrote: Vincent Delecroix wrote: However, running the patchbot on the same computer I got one failing doctest Failed example: G.canonical_label(certify=True) Expected: doctest:...: DeprecationWarning: use the option 'certificate' instead

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

On 27/08/16 22:02, leif wrote: Vincent Delecroix wrote: > > [...] > b) as is, the representation returned for a vertex-labeled graph isn't canonical... ;-) It might if the graph has an automorphism! Vincent -- You received this message because you are subscribed to the Goog

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

vertices, {'a': 0, 'b': 1}) Got: doctest:warning ... DeprecationWarning: use the option 'certificate' instead of 'certify' See http://trac.sagemath.org/2 for details. (Graph on 2 vertices, {'a': 1, 'b': 0}) On 27/08/16 00:11, Vincent Delecroix wrote: Builds and tests long

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

Builds and tests long pass on Ubuntu 14.04.5 LTS (gcc version 4.8.4). Vincent -- 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 7.4.beta1 released

On 17/08/16 17:28, 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 > > 7b1b3ec Updated SageMath version to 7.4.beta1 Several doctest

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

Hi Eric, I guess it comes from #19213 (that assumes that pip is installed). #21291 is likely to solve the issue. Vincent On 19/08/16 17:56, Eric Gourgoulhon wrote: Hi, On Ubuntu 16.04.1, after a fresh git clone + git pull origin develop + make, build failed with the message

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

On 28/03/16 20:12, Dima Pasechnik wrote: On Monday, March 28, 2016 at 11:29:08 PM UTC+1, vdelecroix wrote: Yes I do. I see. Having plot code that is sensitive to the LP solver is bad. Is there already a ticket opened? I always maintained that the design when installation of a solver makes

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

#20315 On 28/03/16 19:31, Vincent Delecroix wrote: Indeed, minimal failing example sage: L = Link([[2,1,4,5], [5,6,7,3], [6,4,1,9], [9,2,3,7]]) sage: L.plot() Traceback (most recent call last): ... MIPSolverException: 'CPLEX: The primal has no feasible solution' On 28/03/16 19:29, Vincent

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

Yes I do. I see. Having plot code that is sensitive to the LP solver is bad. Is there already a ticket opened? On 28/03/16 19:19, Volker Braun wrote: I take it you haev CPLEX installed... On Monday, March 28, 2016 at 11:20:01 PM UTC+2, vdelecroix wrote: Hello, I got problems building the

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

Hello, I got problems building the doc for "knots" (see attached log obtained without parallel build). I am alone in that case? Vincent On 28/03/16 12:16, Volker Braun wrote: As always, you can get the latest beta version from the "develop" git branch. Alternatively, the self-contained

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

docclean -> doc-clean On 08/09/15 11:59, Anne Schilling wrote: Hi! When I tried to install the latest version of Sage, I get the following error messages (even after `make docclean') on OSX10.10.5. Best, Anne [repl ] reading sources... [ 2%] environ [tensor_fr] reading sources... [

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

After looking at the code, it seems that GAP is involved in the background (all commands correspond to calling GAP). Our interface might have some problems. I wonder what is this Bad exit: 2 Which program wrote that in the log? Vincent On 18/08/15 22:43, Justin C. Walker wrote: By attached

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

Rebuilt from scratch, got one failure with ptestlong sage -t --long src/sage/schemes/toric/weierstrass.py ** File src/sage/schemes/toric/weierstrass.py, line 478, in sage.schemes.toric.weierstrass.WeierstrassForm Failed example:

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

On 15/05/15 10:16, Volker Braun wrote: On Friday, May 15, 2015 at 10:07:24 AM UTC+2, vdelecroix wrote: AttributeError: 'MatrixSpace_with_category' object has no attribute 'scheme' I've seen that one before (randomly, pretty rare). If I run independently sage -t --long on this file

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

$ make ptestlong -- All tests passed! -- (ubuntu x86_64) On 14/05/15 01:57, Volker Braun wrote: As usual, get the develop git branch. We now measure the

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

I am facing the following when running tests in parallel {{{ sage -t --long src/sage/interfaces/expect.py ** File src/sage/interfaces/expect.py, line 792, in sage.interfaces.expect.Expect._eval_line Failed example:

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

On 19/04/15 12:49, Marc Mezzarobba wrote: On my machine, sage -t --verbose src/sage/rings/integer.pyx blocks on: Trying (line 6089):alarm(0.5); (2^100).binomial(2^22, algorithm='pari') Expecting: Traceback (most recent call last): ... AlarmInterrupt Is that a known

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

make ptestlong gives sage -t --long src/sage/interfaces/maxima.py ** File src/sage/interfaces/maxima.py, line 254, in sage.interfaces.maxima Failed example: _ = maxima.eval(f(t) := t*sin(t)) Exception raised: Traceback

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

(sage.categories.action.PrecomposedAction at 0x2b41eb2a2050) failed: RuntimeError: This action acted on a set that became garbage collected which is similar to #18157. Forget the previous file which was run with sage-6.2!!! Vincent On 12/04/15 22:15, Vincent Delecroix wrote: Hello, Got troubles (after make

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

At least, does 'sage -i openssl' before 'make' work? On 08/04/2015, Volker Braun vbraun.n...@gmail.com wrote: Yes it does. On Wednesday, April 8, 2015 at 12:22:41 PM UTC+2, vdelecroix wrote: On 08/04/2015, Volker Braun vbrau...@gmail.com javascript: wrote: OpenSSL is not GPL compatible, so

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

On 08/04/2015, leif not.rea...@online.de wrote: On 04/08/2015 12:48 PM, 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). It used to work and hence still *should

Re: [sage-release] Re: Error building sagenb

On 07/04/2015, Volker Braun vbraun.n...@gmail.com wrote: On Tuesday, April 7, 2015 at 1:04:57 PM UTC+2, Simon King wrote: PS: Where do I get the missing dependencies from? Apparently it was not enough to get libopenssl and libopenssl-devel (previously, I had libopenssl in 32 bit version, even

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

On debian jessie 64bits: build without any problems (make distclean; make) But I got some doctest failures when running them in parallel: sage -t --long sage/calculus/desolvers.py # 8 doctests failed sage -t --long sage/tests/french_book/integration_doctest.py # 1 doctest failed sage -t --long

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

With make ptestlong -- sage -t --long src/sage/interfaces/expect.py # 1 doctest failed -- But then running sage -t --long src/sage/interfaces/expect.py it

[sage-release] recent trouble with ubuntu package

Dear Jan (cc-ed sage-devel and sage-release), It seems that the most recent package for ubuntu break the R interface. See the report at: http://ask.sagemath.org/question/25189/cannot-allocate-memory/ Best, Vincent -- You received this message because you are subscribed to the Google Groups

[sage-release] Re: recent trouble with ubuntu package

in this session --- Warning message: package ‘test’ is not available (for R version 3.1.1) Can anyone else reproduce this? Regards, Jan On 10 December 2014 at 10:12, Vincent Delecroix 20100.delecr...@gmail.com wrote: Dear Jan (cc-ed sage-devel and sage-release), It seems that the most recent

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

On the very same file, I get another strange one: $ sage -t --long generic_graph.py too few successful tests, not using stored timings Running doctests with ID 2014-11-27-17-54-33-1df65b61. Doctesting 1 file. sage -t --long generic_graph.py

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

, 27 Nov 2014 17:58:56 Vincent Delecroix wrote: On the very same file, I get another strange one: $ sage -t --long generic_graph.py too few successful tests, not using stored timings Running doctests with ID 2014-11-27-17-54-33-1df65b61. Doctesting 1 file. sage -t --long generic_graph.py

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

Only 46% of ticket on combinatorial designs... we have to work harder! Vincent 2014-08-28 20:49 UTC+02:00, Volker Braun vbraun.n...@gmail.com: Git develop branch. Source tarball: http://boxen.math.washington.edu/home/release/sage-6.4.beta2.tar.gz Mini-changelog: 95c1030 Trac #16890: