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

2023-10-16 Thread Sébastien Labbé
On Ubuntu 18.04 with the following optional packages, Using --optional=4ti2,antic,build,cbc,ccache,cryptominisat,debian,dot2tex,e_antic,external,fricas,glucose,kissat,latte_int,lidia,normaliz,pip,sage,sage_numerical_backends_coin,sage_spkg I get

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

2023-04-04 Thread Sébastien Labbé
this is probably due to https://github.com/sagemath/sage/pull/35093/commits/99901632beaa604331bca3d82eb5347bc43fc14e Could you edit the corresponging installed file in local/ and see if this starts passing. If so, please open an issue. I changed the false to true. The error is still

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

2023-04-03 Thread Sébastien Labbé
On Ubuntu 18.04, running tests with few optional and external packages, I get: Using

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

2023-02-02 Thread Sébastien Labbé
On Thursday, February 2, 2023 at 7:37:27 PM UTC+1 matthia...@gmail.com wrote: On Thursday, February 2, 2023 at 9:30:30 AM UTC-8 Sébastien Labbé wrote: ./bootstrap: 9: m4: Permission denied make: *** [Makefile:365 : configure] Erreur 1 Do you have "." in PATH? No What does &quo

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

2023-02-02 Thread Sébastien Labbé
On Thursday, February 2, 2023 at 6:31:21 PM UTC+1 John H Palmieri wrote: Some people have had an issue with Singular: the system version is too new. Using "./configure --with-system-singular=no" (probably after "make distclean"?) would help, if that's the problem. There is an upgrade ticket for

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

2023-02-02 Thread Sébastien Labbé
On another machine running Ubuntu 22.04, installing sage from source from scratch, I get "m4: Permission denied" error during the "make configure". Should I "sudo make configure" ? Never done that before... See below: $ make configure ./bootstrap -d make[1] : on entre dans le répertoire «

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

2023-02-02 Thread Sébastien Labbé
Thanks for the release. On my side, I am stuck with the following. I was having the same issue with the previous version. I saw I was not alone, but I still don't know what is the solution? Anybody know? Make distclean? Sébastien [sagelib-9.8.rc0] installing. Log file:

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

2023-01-13 Thread Sébastien Labbé
On Ubuntu 18.04, I managed to make build and doc ok with cython capabilities: $ sage ┌┐ │ SageMath version 9.8.beta6, Release Date: 2022-12-21 │ │ Using Python 3.10.8. Type "help()" for help.

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

2022-12-12 Thread Sébastien Labbé
On Ubuntu 18.04 + optional packages, I get: Using --optional=build,debian,dot2tex,external,glucose,pip,sage,sage_spkg Features to be detected:

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

2022-11-07 Thread Sébastien Labbé
On Ubuntu 18.04, with few optional/external packages, here is what I get: Running with SAGE_LOCAL='/home/slabbe/GitBox/sage/local' and SAGE_VENV='/home/slabbe/GitBox/sage/local/var/lib/sage/venv-python3.10.8' Using --optional=build,debian,external,glucose,pip,sage,sage_spkg Features to be

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

2022-10-21 Thread Sébastien Labbé
On Ubuntu 18.04, here is what I get with few optional/external packages: Using --optional=build,debian,external,glucose,pip,sage,sage_spkg Features to be detected:

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

2022-10-06 Thread Sébastien Labbé
On a machine running Ubuntu 20.04 + some optional and external packages, I obtain: Using

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

2022-09-27 Thread Sébastien Labbé
After upgrading my gcc, g++ and gfortran to 9, I managed to build and test with a bunch of optional and external packages. I get the following list of failures. Using --optional=build,debian,external,glucose,pip,sage,sage_spkg Features to be detected:

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

2022-06-23 Thread Sébastien Labbé
On Ubuntu 18.04, I get Git branch: develop Git ref: 9.7.beta3 Running with SAGE_LOCAL='/home/slabbe/GitBox/sage/local' and SAGE_VENV='/home/slabbe/GitBox/sage/local/var/lib/sage/venv-python3.10.3' Using --optional=build,debian,external,pip,sage,sage_spkg Features to be detected:

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

2022-06-01 Thread Sébastien Labbé
On Ubuntu 20.04 + few optional packages, I get: Using --optional=4ti2,build,ccache,cryptominisat,debian,dot2tex,e_antic,external,fricas,glucose,latte_int,lidia,lrslib,normaliz,notedown,pandoc_attributes,pip,pycosat,pynormaliz,rst2ipynb,sage,sage_numerical_backends_coin,sage_spkg ...

[sage-release] Re: Sage 9.6 released

2022-05-17 Thread Sébastien Labbé
Thanks for the release! Sébastien On Monday, May 16, 2022 at 12:27:40 AM UTC+2 Volker Braun wrote: > The "master" git branch has been updated to Sage-9.6. As always, you can > get the latest beta version from the "develop" git branch. Alternatively, > the self-contained source tarball is at >

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

2022-05-02 Thread Sébastien Labbé
Thanks for the release. On Ubuntu 18.04, with some optional and external packages installed, I get: -- sage -t --long --random-seed=10041023278531363329797553849793068311 src/sage/combinat/designs/incidence_structures.py # 1

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

2022-04-20 Thread Sébastien Labbé
Testing with few optional and external packages on Ubuntu 18.04, I get failures with 8 files: -- sage -t --long --random-seed=244716197900726204861772829584257473787

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

2022-04-11 Thread Sébastien Labbé
On Ubuntu 18.04, running doctests with few optional and external tags, I get: Using

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

2022-03-29 Thread Sébastien Labbé
With Ubuntu 18.04, and running doctests with few optional/external packages, I get: -- sage -t --long --random-seed=4345853567077574058850080858948729205 src/sage/combinat/designs/incidence_structures.py # 1 doctest failed

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

2022-02-24 Thread Sébastien Labbé
On Ubuntu 18.04, running tests with few optional and external packages, I get Using

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

2022-02-16 Thread Sébastien Labbé
After `make distclean`, I managed to let make complete correctly. So on Ubuntu 18.04 with few optional and external packages installed, running tests gives Running doctests with ID 2022-02-16-13-33-33-bf595c7c. Git branch: develop Using

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

2022-02-15 Thread Sébastien Labbé
Trying to update from recent version, I get: [sagemath_doc_html-none] installing. Log file: /home/slabbe/GitBox/sage/logs/pkgs/sagemath_doc_html-none.log [sagemath_doc_html-none] error installing, exit status 2. End of log file:

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

2022-02-08 Thread Sébastien Labbé
On Ubuntu 18.04, with few optional/external packages, I get Running doctests with ID 2022-02-07-17-21-38-2cb12a08. Git branch: develop Using

[sage-release] Re: Sage 9.5 released

2022-01-31 Thread Sébastien Labbé
On Sunday, January 30, 2022 at 4:48:26 PM UTC+1 Volker Braun wrote: > The "master" git branch has been updated to Sage-9.5. 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] Sage 9.5.rc4 released

2022-01-25 Thread Sébastien Labbé
> > > Built w/o problems on two macOS systems, as indicated in the attached > logs, below, with testing errors (‘ptestlong’): > > I created https://trac.sagemath.org/ticket/33231 for the second of the three errors. -- You received this message because you are subscribed to the Google Groups

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

2022-01-25 Thread Sébastien Labbé
On Ubuntu 18.04, running tests with optional/external packages, I get Using

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

2022-01-25 Thread Sébastien Labbé
> As suggested, I did "make doc-clean doc-uninstall" and I am currently > waiting for the result of make. > It worked: [sagemath_doc_html-none] Build finished. -- You received this message because you are subscribed to the Google Groups "sage-release" group. To unsubscribe from this

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

2022-01-25 Thread Sébastien Labbé
Upgrading from a recent rc, I get an error with doc building: [sagemath_doc_html-none] installing. Log file: /home/slabbe/GitBox/sage/logs/pkgs/sagemath_doc_html-none.log [sagemath_doc_html-none] error installing, exit status 2. End of log file:

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

2022-01-21 Thread Sébastien Labbé
es". Sincerely, Sébastien Labbé On Wednesday, January 19, 2022 at 1:05:13 AM UTC+1 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/downlo

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

2022-01-21 Thread Sébastien Labbé
Thanks Volker for the release. My first try at building with configuration $ ./configure --enable-experimental-packages --enable-download-from-upstream-url --enable-ccache --enable-dot2tex --enable-rst2ipynb --enable-openssl --enable-cbc --enable-cryptominisat --enable-pycosat

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

2022-01-14 Thread Sébastien Labbé
On Ubuntu 20.04, running tests with various optional and external packages (including internet optional tag), I obtain: Using

[sage-release] Re: after edit the sage library, sage -b now tells "Nothing to (re)build / all up-to-date."

2022-01-14 Thread Sébastien Labbé
janvier 2022 à 15:44:15 UTC+1, Sébastien Labbé a écrit : > >> With 9.5.rc0, I modify a file in the sage library, then >> >> $ sage -b >> Nothing to (re)build / all up-to-date. >> >> does nothing. This is a new behavior. But it seems my modications are >&g

[sage-release] Re: after edit the sage library, sage -b now tells "Nothing to (re)build / all up-to-date."

2022-01-14 Thread Sébastien Labbé
oups, I wanted to post that to sage-devel. Sorry. -- 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 view this

[sage-release] after edit the sage library, sage -b now tells "Nothing to (re)build / all up-to-date."

2022-01-14 Thread Sébastien Labbé
With 9.5.rc0, I modify a file in the sage library, then $ sage -b Nothing to (re)build / all up-to-date. does nothing. This is a new behavior. But it seems my modications are being considered, so it is okay. >From where does this change in behavior come from? -- You received this message

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

2022-01-14 Thread Sébastien Labbé
On Friday, January 14, 2022 at 10:10:00 AM UTC+1 egourg...@gmail.com wrote: > This is a permanent failure: > sage -t --long --warn-long 67.0 > --random-seed=127661401430613686989226810121136436198 > src/sage/game_theory/parser.py > A ticket exists for this issue:

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

2022-01-13 Thread Sébastien Labbé
On Ubuntu 20.04, when I ran `make ptestlong`, I obtain -- sage -t --long --random-seed=277349812120896257585806851727004727044 src/sage/sat/boolean_polynomials.py # 18 doctests failed sage -t --long

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

2022-01-11 Thread Sébastien Labbé
Dear Volker, I would also like to ask whether it is possible to include https://trac.sagemath.org/ticket/20343 in the next rc? It got a positive review last Thursday. It adds a new module sage/plot/tikzpicture.py to deal with tikzpicture, show them automatically in a Jupyter cell and export

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

2022-01-10 Thread Sébastien Labbé
On Monday, January 10, 2022 at 1:52:51 PM UTC+1 Sébastien Labbé wrote: > My first attempt at building the new version finishes with what is copied > below (from make with V=0). I get the same thing after `make doc-clean` and > also `make doc-uninstall`, a new command which I have seen

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

2022-01-10 Thread Sébastien Labbé
My first attempt at building the new version finishes with what is copied below (from make with V=0). I get the same thing after `make doc-clean` and also `make doc-uninstall`, a new command which I have seen recently. [sagemath_doc_html-none] installing. Log file:

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

2021-12-29 Thread Sébastien Labbé
On Ubuntu 20.04, make build works fine and running tests with few optional and external packages I get: Using

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

2021-12-16 Thread Sébastien Labbé
On Ubuntu 18.04, running tests with few optional/external packages gives: Using

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

2021-11-26 Thread Sébastien Labbé
Again, running ./sage -t -p --all --long --optional=sage,optional,external,build --show-skipped stops at findstat.py. Also src/sage/combinat/designs/ext_rep.py seems to again be among the tests that are killed: 0: Mp00061oMp00069 (quality [100]) Got: 0: Mp00061oMp00069 (quality [97])

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

2021-11-25 Thread Sébastien Labbé
On Ubuntu 18.04, running tests with many optional and external packages, the tests stops at some point and among the files that are killed at this point are findstat.py and doctest/external.py. More precisely, Using

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

2021-11-16 Thread Sébastien Labbé
The 9 failing doctests in cmdline.py are related to the fact that sage --standard, sage --optional and sage --experimental are currently broken. I created ticket https://trac.sagemath.org/ticket/32885 for it. -- You received this message because you are subscribed to the Google Groups

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

2021-11-16 Thread Sébastien Labbé
On Ubuntu 18.04, testing with few optional and external packages gives: -- sage -t --long --random-seed=132752562576186471630888746423217429031 src/sage/combinat/designs/incidence_structures.py # 1 doctest failed sage -t --long

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

2021-11-04 Thread Sébastien Labbé
> In the second case it looks to me as if it is only that the list has > the same matrices in a different order. > The ordering failure in src/sage/dynamics/arithmetic_dynamics/projective_ds.py is dealt here: https://trac.sagemath.org/ticket/32817 (currently needs review) -- You received

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

2021-11-04 Thread Sébastien Labbé
On Ubuntu 18.04 with few optional and external packages, I get: Using

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

2021-10-22 Thread Sébastien Labbé
On Ubuntu 18.04 with many optional and external packages, I get Using

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

2021-10-14 Thread Sébastien Labbé
I just created 5 tickets for the above new failures. Follow up at https://trac.sagemath.org/ticket/25536 -- 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] Re: Sage 9.4.beta4 released

2021-07-02 Thread Sébastien Labbé
On Ubuntu 18.04, running tests with few optional and external packages, I get: Using

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

2021-06-29 Thread Sébastien Labbé
On Monday, June 28, 2021 at 6:12:01 AM UTC+2 tsc...@ucdavis.edu wrote: > I also ran into the same problem as Sébastien on Ubuntu 18.04 LTS and > would like a better solution than just having to manually configure the > Python version. > > It should be fixed by

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

2021-06-24 Thread Sébastien Labbé
Doing make distclean and using system's python3.8 with ./configure --with-python=/usr/bin/python3.8 avoided my issue with compilation of python3.9.5. On Ubuntu 18.04, make ptestall with following optional and external packages gives: Using

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

2021-06-24 Thread Sébastien Labbé
Upgrading from 9.4.beta0, my first attempt with running make finishes with: [python3-3.9.5] error installing, exit status 1. End of log file: [python3-3.9.5] File "/home/slabbe/GitBox/sage/local/var/tmp/sage/build/python3-3.9.5/src/./setup.py", line 33, in [python3-3.9.5] from

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

2021-05-27 Thread Sébastien Labbé
> Probably the "period" / "full stop" at the very end. > > > ... 292, ...] > > ... 292, ...]. > Goodeye, goodeye! Needs review at: https://trac.sagemath.org/ticket/31865 https://trac.sagemath.org/ticket/31866 Also the random failure with graph.py was noticed by Volker already:

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

2021-05-27 Thread Sébastien Labbé
I have python3.6 and python3.8 installed on my system: $ python3 Python 3.6.9 (default, Jan 26 2021, 15:33:00) [GCC 8.4.0] on linux Type "help", "copyright", "credits" or "license" for more information. >>> $ python3.8 Python 3.8.0 (default, Feb 25 2021, 22:10:10) [GCC 8.4.0] on linux Type

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

2021-05-27 Thread Sébastien Labbé
On Ubuntu 18.04, testing with various optional and external packages, I obtain: -- sage -t --long --warn-long 77.6 --random-seed=0 src/sage/databases/oeis.py # 3 doctests failed sage -t --long --warn-long 77.6 --random-seed=0

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

2021-05-27 Thread Sébastien Labbé
Thank you for the release. I observe that #21295 was merged twice: 12831dd5b0 Trac #21295: recognizable series (a base for k-regular sequences) 7f610a53c0 Trac #21295: recognizable series (a base for k-regular sequences) It is the first time that I see such a thing. Sébastien On Wednesday, May

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

2021-03-25 Thread Sébastien Labbé
On Ubuntu 18.04, with various optional/external packages, I get: Using

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

2021-03-09 Thread Sébastien Labbé
On Ubuntu 18.04, with few optional/external packages, I get: Using

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

2021-02-09 Thread Sébastien Labbé
On Ubuntu 18.04, running tests with various optional/external packages, I get: Using

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

2021-02-09 Thread Sébastien Labbé
Sorry for the late reply on the 9.3.beta6 thread, but it may be helpful for comparisons. On Ubuntu 18.04, with few optional and external packages, I get: Using

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

2020-12-30 Thread Sébastien Labbé
On Ubuntu 18.04, testing various optional and external packages, I get: Using

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

2020-12-15 Thread Sébastien Labbé
On Ubuntu 18.04, testing with various optional and external packages, I get: Using

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

2020-12-07 Thread Sébastien Labbé
On Ubuntu 18.04, testing various optional and external packages, and using

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

2020-11-25 Thread Sébastien Labbé
On Ubuntu 18.04, running tests with various optional and external packages, I get: Using

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

2020-11-08 Thread Sébastien Labbé
On Ubuntu 18.04, running tests with various optional and external packages, I get Using

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

2020-11-01 Thread Sébastien Labbé
On Ubuntu 18.04 with python3.8.0 installed, testing few optional and external packages, I obtain: Using

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

2020-10-26 Thread Sébastien Labbé
> > Thanks, Volker, for preparing the release! > Yes, thanks Volker for the release and everyone. > > > The 9.2 changelog is available at > https://github.com/sagemath/website/pull/208/files > https://github.com/sagemath/website/blob/master/src/changelogs/sage-9.2.txt > > See also the

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

2020-10-23 Thread Sébastien Labbé
> Using Ubuntu 18.04, trying to test with optional + external packages, I still get the tests to stop at half of the execution, and I still don't know why. Reducing the number of CPUs to -j5 instead of -j8, I managed to get all tests to run. I get no other failures than the one reported above:

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

2020-10-22 Thread Sébastien Labbé
Using Ubuntu 18.04, trying to test with optional + external packages, I still get the tests to stop at half of the execution, and I still don't know why. The exact command I run is: ./sage -t -p --all --long --optional=sage,optional,external --show-skipped

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

2020-10-07 Thread Sébastien Labbé
> So apparently my system python3 is used which is Python 3.6.9. The option > capture_output has been introduced in python 3.7. The change introducing > capture_output might have been introduced in Trac #30606. > > Oups, I did the review of #30606 on a machine with Python 3.8 installed (I

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

2020-10-02 Thread Sébastien Labbé
On Ubuntu 16.04, testing few optional and external package, I get Using

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

2020-09-22 Thread Sébastien Labbé
> > I copy paste below the failures: > Just created tickets #30632 to #30638 to deal with the doctest failures I reported earlier. Follow up at https://trac.sagemath.org/ticket/25536 -- You received this message because you are subscribed to the Google Groups "sage-release" group. To

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

2020-09-22 Thread Sébastien Labbé
On Ubuntu 18.04, Running tests with few optional and external packages (including internet this time), I obtain Using

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

2020-09-14 Thread Sébastien Labbé
Answering a question from few days ago: On Thursday, September 10, 2020 at 5:13:00 PM UTC+2 matthia...@gmail.com wrote: > On Thursday, September 10, 2020 at 6:52:09 AM UTC-7, Sébastien Labbé wrote: >> >> On Ubuntu 18.04, it picks up the python3.6 available

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

2020-09-10 Thread Sébastien Labbé
On Ubuntu 18.04, it picks up the python3.6 available on the machine: ## ## ## Checking whether SageMath should install SPKG python3... ## ## ## configure:29604: checking whether any

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

2020-09-07 Thread Sébastien Labbé
On Monday, September 7, 2020 at 2:48:29 PM UTC+2 Sébastien Labbé wrote: > Again, the doctests gets interrupted with an error OSError: [Errno 24] Too > many open files. Is it related to Python 3.8? > Running tests only with the optional packages (not the external packages),

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

2020-09-07 Thread Sébastien Labbé
Again, the doctests gets interrupted with an error OSError: [Errno 24] Too many open files. Is it related to Python 3.8? ... -- sage -t --long --random-seed=0 src/sage/graphs/generic_graph.py # 2 doctests failed sage -t --long

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

2020-09-07 Thread Sébastien Labbé
I now upgraded to Ubuntu 20.04.1 LTS (which may explains why I am reporting errors below I was not reporting before). Moreover, my config.log confirms that I am using python3.8 from my system: ... ## ## ## Checking whether SageMath should

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

2020-08-19 Thread Sébastien Labbé
Testing with various optional and external packages, I get: Using --optional=4ti2,cbc,ccache,cryptominisat,dot2tex,e_antic,external,fricas,glucose,latte_int,lidia,lrslib,memlimit,normaliz,notedown,openssl,pandoc_attributes,pycosat,pynormaliz,rst2ipynb,sage,sage_numerical_backends_coin

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

2020-08-14 Thread Sébastien Labbé
Running tests with few optional and external packages (but not internet due to some issue with my current installation), I get Using

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

2020-07-31 Thread Sébastien Labbé
Running tests with few optional and external packages (but not internet which I think is because I was too far from the wifi), I get Using

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

2020-07-13 Thread Sébastien Labbé
Running tests with few optional and external packages, I get Using

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

2020-07-10 Thread Sébastien Labbé
Running tests with various optional+external packages, I get Using

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

2020-06-29 Thread Sébastien Labbé
Runing tests with few optional/external packages, Using

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

2020-06-24 Thread Sébastien Labbé
Testing various optional and external packages (on June 15, but I am reporting only now sorry for the delay), I get Using

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

2020-06-03 Thread Sébastien Labbé
Testing various optional and external packages, I get Using

[sage-release] Re: Sage 9.1.rc4 released!

2020-05-11 Thread Sébastien Labbé
On Monday, May 11, 2020 at 12:10:41 PM UTC+2, Jonathan Kliem wrote: > > The deprecation warning is the tested output in polyhedron/base.py line > 9278. > > affine_hull was deprecated in https://trac.sagemath.org/ticket/29326. > > I don't see why this test shouldn't pass as it uses the same

[sage-release] Re: Sage 9.1.rc4 released!

2020-05-11 Thread Sébastien Labbé
Testing many optional and external packages, I get Using --optional=4ti2,cbc,ccache,cryptominisat,dot2tex,e_antic,external,fricas,glucose,latte_int,lidia,lrslib, memlimit,normaliz,notedown,openssl,pandoc_attributes,pycosat,pynormaliz,rst2ipynb,sage,sage_numerical_backends_coin,

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

2020-05-07 Thread Sébastien Labbé
Testing few optional and external packages, I get: Using --optional=4ti2,cbc,ccache,cryptominisat,dot2tex,e_antic,external,fricas,glucose,latte_int,lidia,lrslib,memlimit, normaliz,notedown,openssl,pandoc_attributes,pycosat,pynormaliz,rst2ipynb,sage,sage_numerical_backends_coin,

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

2020-04-30 Thread Sébastien Labbé
Using the following configuration: $ head config.log ... $ ./configure --enable-experimental-packages --enable-download-from-upstream-url --enable-ccache --enable-dot2tex --enable-rst2ipynb --enable-openssl --enable-cbc --enable-cryptominisat --enable-pycosat --enable-glucose

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

2020-04-30 Thread Sébastien Labbé
It seems that if I do ./configure --enable-beautifulsoup4 or ./configure --enable-pyopenssl I get make[3]: *** Aucune règle pour fabriquer la cible « /home/slabbe/GitBox/sage/local/var/lib /sage/installed/beautifulsoup4-none », nécessaire pour « all-sage ». Arrêt. make[3]: *** Attente des

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

2020-04-30 Thread Sébastien Labbé
Ok, I see, I thought it was in already. Maybe that's the reason why my make finishes with an error. Let me try to run make again without that option. Will report later. -- You received this message because you are subscribed to the Google Groups "sage-release" group. To unsubscribe from this

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

2020-04-30 Thread Sébastien Labbé
I am now using ./configure --enable-silent-rules instead of export V=0 and it seems not to work as make is full verbose now. Am I doing something wrong? -- You received this message because you are subscribed to the Google Groups "sage-release" group. To unsubscribe from this group and

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

2020-04-25 Thread Sébastien Labbé
Testing few optional and external packages, here is what I get: Using

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

2020-04-15 Thread Sébastien Labbé
Running tests with few optional and external packages, here is what I get: Using --optional=4ti2,cbc,ccache,cryptominisat,dot2tex,e_antic,external,glucose,latte_int,lidia,lrslib,memlimit, normaliz,notedown,openssl,pandoc_attributes,pycosat,pynormaliz,rst2ipynb,sage,sage_numerical_backends_coin,

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

2020-03-31 Thread Sébastien Labbé
Testing with many optional and external packages, I get Using

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

2020-03-20 Thread Sébastien Labbé
Runing tests with few optional + external packages, I get Using

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

2020-03-09 Thread Sébastien Labbé
Running few optional + external packages, I get Using

  1   2   3   >