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

Bonjour sage-release, On Wednesday, April 2, 2014 2:09:20 AM UTC+2, Volker Braun wrote: Get it from the develop git branch or the source tarball at http://boxen.math.washington.edu/home/release/sage-6.2.beta6/sage-6.2.beta6.tar.gz I get an error while building matplotlib1-3.1. It seems

### [sage-release] Re: Sage 6.2 released

Hi sage-release, I get an error with the compilation of sage/graphs/distances_all_pairs.c. Here is what I did: $ git checkout master $ git pull --ff-only github master $ make distclean $ make [...] Host system: Darwin pol 9.8.0 Darwin Kernel

### [sage-release] Re: Sage 6.2 released

On Thursday, May 8, 2014 9:54:58 PM UTC+2, Peter Bruin wrote: Hello, It looks like (the automatically generated) distances_all_pairs.c is the result of an interrupted/failed Cython compilaton. My copy of that file is 14706 lines long and the last line is #endif /* Py_PYTHON_H */

### [sage-release] Re: Sage 6.2 released

$ make [...] Updating Cython code Compiling sage/graphs/distances_all_pairs.pyx because it changed. Found compiled sage/graphs/distances_all_pairs.pyx in cache Finished Cythonizing, time: 10.05 seconds. [...] and then the same error again. I need to delete the compiled

### [sage-release] Re: Sage 6.2 released

On Thursday, May 8, 2014 11:17:53 PM UTC+2, Peter Bruin wrote: The Cython cache seems to be ~/.cycache/, at least on my system. thanks! now it works : [...] Updating Cython code Compiling sage/graphs/distances_all_pairs.pyx because it changed. Cythonizing

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

All tests passed with make ptestlong on ubuntu 14.04 x86_64. Sébastien -- 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.

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

On Ubuntu 14.04 x86_64, after updating to github master and running make distclean, sage-6.7 builds fine and starts, documentation builds fine but make ptestlong finishes with 220 files having failing doctests all of them related to missing optional package (I think make distclean removes them

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

On Tuesday, May 19, 2015 at 10:12:23 AM UTC+2, Jeroen Demeyer wrote: Did you run make ptestlong or make ptestall? You are right. I did make ptestall. -- You received this message because you are subscribed to the Google Groups sage-release group. To unsubscribe from this group and stop

### [sage-release] Re: Sage 6.7.beta0 released

On ubuntu 14.04 64 bit make ptestlong gives 266 files with 1 failing doctest, always the same warning: sage -t --long src/doc/de/thematische_anleitungen/sage_gymnasium.rst ** File

### [sage-release] Re: Sage 6.7.beta0 released

On Thursday, April 16, 2015 at 11:05:11 AM UTC+2, Dima Pasechnik wrote: chmod 700 ~/.sage/.python-eggs should fix this Indeed: All tests passed! -- You received this message because you are subscribed to the Google Groups sage-release group. To unsubscribe from this group and stop

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

On Wednesday, April 8, 2015 at 1:35:04 PM UTC+2, Volker Braun wrote: bzip2 installed /Users/seb/Applications/sage/local/lib/libbz2.la, but it seems to be gone now. Who deleted it? Nobody, it is still there. Thanks for the follow up. I now understand what is happening. Not only I changed my

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

I get an error with libgd while compiling sage-6.6.rc2 on this machine: $ uname -a Darwin MacBookebastien.home 14.1.0 Darwin Kernel Version 14.1.0: Mon Dec 22 23:10:38 PST 2014; root:xnu-2782.10.72~2/RELEASE_X86_64 x86_64 Full libgd-2.1.0.p0.log is attached to this email. It finishes with: mv

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

On Wednesday, April 8, 2015 at 12:01:29 PM UTC+2, Sébastien Labbé wrote: I get an error with libgd while compiling sage-6.6.rc2 on this machine: Maybe I have an hypothesis for this error... I am currently reinstalling everything from scratch on my machine after I changed the hard disk

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

On Wednesday, April 8, 2015 at 12:20:04 PM UTC+2, Volker Braun wrote: post the bzip2 install log The bzip2 install log is attached. It was successful finishing with: real0m16.313s user0m12.348s sys 0m7.020s Successfully installed bzip2-1.0.6.20140317 Deleting temporary

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

Is there a way to sage -i all optional packages that are used the doctests of the whole sage library? Should make ptestall do that before running tests? On Tuesday, May 19, 2015 at 10:17:17 AM UTC+2, Sébastien Labbé wrote: On Tuesday, May 19, 2015 at 10:12:23 AM UTC+2, Jeroen Demeyer wrote

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

1 - On the first compilation, I get: [algebras ] writing output... [ 96%] sage/algebras/steenrod/steenrod_algebra_mult [algebras ] writing output... [100%] sage/algebras/weyl_algebra [algebras ] dumping object inventory... done [algebras ] build succeeded. [graphs ] reading sources... [ 73%]

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

On OSX 10.10.2, Xcode 6.3, make ptestlong finishes with: -- sage -t --long src/sage/doctest/test.py # Timed out after testing finished -- which is not

### [sage-release] Re: Sage 6.8.beta8 released

On Ubuntu 14.04 64 bit and using

### [sage-release] Re: Sage 6.9.rc3 released

-- which is not reproducible. Also, I confirm that I also get the display latex problem cited above: > ./sage -n jupyter > In[1]: %display latex > In[2]: sin(x^2) > results in > Out[2]: \newcommand{\Bold}[1]{\mathbf{#1}}\sin\left(x^{2}\right) Sébastien Labbé On Wednesday, October 7, 201

### [sage-release] Re: Sage 6.8.beta7 released

Running make ptestlong on Ubuntu 14.04 and using

### [sage-release] Re: Sage 6.8.beta7 released

But the one in doctest/test.py keeps being there. -- sage -t --long --warn-long 29.8 src/sage/doctest/test.py # 1 doctest failed Needs review at: http://trac.sagemath.org/ticket/18873 -- You received this message

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

On Ubuntu 14.04 64 bit, Using

### Re: [sage-release] Sage-6.10.rc1 released

Similarly, sage: len(str('a')) 1 sage: len(repr('a')) 3 -- You received this message because you are subscribed to the Google Groups "sage-release" group. To unsubscribe from this group and stop receiving emails from it, send an email to sage-release+unsubscr...@googlegroups.com. To post to

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

With optional sage packages coxeter3 and cryptominisat, I get some optional doctests that are broken: -- sage -t --warn-long 27.7 src/sage/rings/polynomial/multi_polynomial_sequence.py # 1 doctest failed sage -t --warn-long

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

On Friday, November 27, 2015 at 3:49:49 PM UTC+1, Sébastien Labbé wrote: > > With optional sage packages coxeter3 and cryptominisat, I get some > optional doctests that are broken: > > -- > sage -t --warn-lon

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

On Ubuntu 14.04 64 bit Using --optional=gcc,mpir,python2,sage make ptestlong finishes with labbe@priminfo sage-git $ tail logs/ptestlong.log sage -t --long --warn-long 27.1 src/sage_setup/docbuild/sphinxbuild.py [0 tests, 0.00 s] sage -t --long --warn-long 27.1

### [sage-release] Re: Sage 7.4.beta6 released

On Ubuntu 16.04, Using --optional=4ti2,atlas,ccache,meataxe,mpir,pandocfilters,python2,sage make ptestlong finishes with: sage -t --long --warn-long 42.7 src/sage/matrix/matrix_integer_dense.pyx Timed out (and interrupt failed)

### [sage-release] Re: Sage 7.4.beta5 released

Using --optional=4ti2,atlas,mpir,python2,sage on Ubuntu 16.04 make ptestlong finishes with "All tests passed". Thank you! -- 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

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

All tests passed on Ubuntu 14.04 with make ptestlong using --optional=mpir,python2,sage Other than the Tutte polynomial one, I get two other slow doctests that are not marked with #long time. I can not confirm whether it is a regression as I don't keep my old version of sage. sage -t --long

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

On Ubuntu 16.04, Using --optional=4ti2,atlas,ccache,meataxe,mpir,pandoc_attributes,pandocfilters,python2,sage make ptestlong finishes with sage -t --long --warn-long 42.6 src/sage/modular/hecke/module.py Timed out ** Tests

### Re: [sage-release] Re: Sage 7.4.rc0 released

On Wednesday, October 12, 2016 at 10:02:40 AM UTC+2, Jeroen Demeyer wrote: > > > Thanks for your report. I saw this error on two of the patchbots too. > > Are you using the Sage-installed GCC package? What is the output of > > $ ./sage --sh -c 'which gfortran; gfortran --version' > $ ./sage

### Re: [sage-release] Sage 7.4.rc0 released

On Wednesday, October 12, 2016 at 12:22:32 PM UTC+2, François wrote: > > I pushed a branch on that ticket to fix what I suspect is > the problem. > If it fixes it, I’ll push upstream since it is a problem > in their default makefile. > > Branch posted on #21689 fixes it! Thanks! Sébastien

### [sage-release] Re: Sage 7.4.rc1 released

>From branch 7.4.rc0 + #21689, I checked out branch 7.4.rc1 and "make start" works because "openblas" was not recompiled (why?). But on branch 7.4.rc1, if I force compilation of openblas with "sage -f openblas", then I get the same problem I reported yesterday in the 7.4.rc0 thread.

### [sage-release] Re: Sage 7.4.rc1 released

> Therefore, I will mark #21689 as a blocker so that it gets included in 7.4. > ... I just realized Jeroen already set #21689 as blocker when he created the ticket. -- You received this message because you are subscribed to the Google Groups "sage-release" group. To unsubscribe from this

### [sage-release] Re: Sage 7.4.rc0 released

On Ubuntu 16.04, running make ptestlong finishes with "Error installing package openblas-0.2.19" with the following line in the openblas-0.2.19.log ./openblas_utest: error while loading shared libraries: libgfortran.so.3: cannot open shared object file: No such file or directory The end of the

### [sage-release] Re: Sage 7.5.beta4 released

On Ubuntu 16.04, I get an error building the documentation (even after make doc-clean && make): [manifolds] /home/labbe/Applications/sage-git/src/doc/en/reference/manifolds/index.rst:4: WARNING: undefined label: tensors-on-free-modules (if the link has no caption the label must precede a

### [sage-release] Re: Sage 7.5.beta6 released

On OS X 10.10.2, make ptestlong has only one already reported failing test ( `sage126` is not defined line 514 in singular.py). Also, I get a strange log file for sqlite which contains a little bit more than the SPKG.txt file : $ cat logs/pkgs/sqlite.log Found local metadata for

### [sage-release] Re: Sage 7.5.beta6 released

> Also, I get a strange log file for sqlite which contains a little bit more > than the SPKG.txt file : > > $ cat logs/pkgs/sqlite.log > I found out that this junk file is created by sage -t src/sage/tests/cmdline.py, I created: https://trac.sagemath.org/ticket/22062 -- You received

### [sage-release] Re: Sage Debian Live 7.4 released

Thank you very much Thierry. It was of great help during Sage Days 79. I also used it recently on a old windows computer not connected to the internet. It gives a second life to this machine:) Sébastien -- You received this message because you are subscribed to the Google Groups

### [sage-release] Re: Sage 7.5.beta5 released

> > make ptestlong creates two sage.png file due to #21947 (I will create a > ticket to fix this shortly) > https://trac.sagemath.org/ticket/22009 -- You received this message because you are subscribed to the Google Groups "sage-release" group. To unsubscribe from this group and stop

### [sage-release] Re: Sage 7.5.beta4 released

On OSX 10.10.2, I get two errors with make ptestlong (only the one with singular.py reappears on a rerun) : sage -t --long --warn-long 263.5 src/sage/misc/trace.py ** File "src/sage/misc/trace.py", line 66, in

### [sage-release] Re: Sage 7.5.beta4 released

On Tuesday, November 29, 2016 at 11:25:40 AM UTC+1, Sébastien Labbé wrote: > > On Ubuntu 16.04, I get an error building the documentation (even after > make doc-clean && make): > I had uncommited changes in my repo (reverting cython version to 0.24 for testing purpo

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

> ImportError: No module named interpreters.wrapper_rdf > > Again, Eek! > Justin > It was also reported in Cannot build Sage 7.5.beta6 inside Docker, Dec 16, 2016 https://groups.google.com/d/topic/sage-devel/JkUfCPxoi80/discussion The part " 'sage_setup.docbuild' is a package and cannot

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

On Ubuntu 16.04, git pull develop from 7.5.beta6 and make ptestlong has only one failing (timed out) test: sage: from sage.doctest.external import has_mathematica ## line 111 ## sage: has_mathematica() # random ## line 112 ##

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

On Thursday, March 23, 2017 at 9:07:54 AM UTC+1, vdelecroix wrote: > > On 13/02/2017 14:32, Sébastien Labbé wrote: > > > > Also git status now tells me I have this file in SAGE_ROOT: > > > > octave-workspace > > > > ? > > How did you

### [sage-release] Re: Sage 8.0.rc0 released

On Ubuntu 16.04, make ptestlong finishes with two doctest failures that were already reported on this mailing list. Both doctests pass when run separately. -- sage -t --long --warn-long 61.4

### [sage-release] Re: Sage 8.0.beta3 released

On OSX 10.10 Yosemite, without #22860, make ptestlong yields only one failed already reported doctest: NotImplementedError: Unable to parse Giac output: integrate(t^n*exp(-s*t),t,0,+infinity) -- You received this message because you are subscribed to the Google Groups "sage-release"

### [sage-release] Re: Sage 8.0.beta9 released

On osx 10.10, make ptestlong gives 2 doctest errors (which are not reproducible): sage -t --long src/sage/tests/cmdline.py ** File "src/sage/tests/cmdline.py", line 208, in sage.tests.cmdline.test_executable Failed example:

### [sage-release] Re: Sage 8.0.beta11 released

> Thanks Volker! This is indeed the case: I've recently added the line > %colors Linux > to the file ~/.sage/init.sage > Removing it fixes the problem. > It is better to set colors Linux in the file profile_default/ipython_config.py see

### [sage-release] Re: Sage 8.0.beta11 released

On osx 10.10, make ptestlong gives: All test passed! On Ubuntu 16.04, make ptestlong gives -- sage -t --long --warn-long 61.1 src/sage/sat/boolean_polynomials.py # 1 doctest failed

### [sage-release] Re: Sage 8.1.beta7 released

On a recent dell machine running Ubuntu 16.06, I get one failing test during make ptestlong. The test pass when run alone : sage -t --long src/sage/libs/gap/assigned_names.py ** File "src/sage/libs/gap/assigned_names.py", line

### [sage-release] Re: Sage 8.1.beta9 released

On Ubuntu 16.04 make ptestlong gives All tests passed! Thank you, Sébastien On Sunday, October 22, 2017 at 7:22:18 PM UTC+2, 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 >

### [sage-release] Re: Sage 8.1.rc3 released

On Ubuntu 16.04, I get problem building python2-2.7.14.p2 during make ptestlong. The error is reproducable when I perform sage -i python2 End of log is below ... gcc -pthread -shared -L. -L/home/slabbe/GitBox/sage/local/lib -Wl,-rpath,/home/slabbe/GitBox/sage/local/lib -L.

### [sage-release] Re: Sage 8.1.rc3 released

> ImportError: No module named _ctypes > ctypes module failed to import > math module imported OK > hashlib module imported OK > crypt module imported OK > readline module imported OK > socket module imported OK > Error: One or more modules failed to import. > > real2m25.869s > user

### [sage-release] Re: Sage 8.1.rc3 released

... and I get "All tests passed!" after make ptestlong. Thank you. -- 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

### [sage-release] Re: Sage 8.2.beta0 released

I get 5 failing # optional - rst2ipynb doctests. log below. -- sage -t --long --warn-long 59.5 src/sage/tests/cmdline.py # 5 doctests failed -- sage -t

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

On Tuesday, May 15, 2018 at 9:24:26 PM UTC+2, Sébastien Labbé wrote: > > On Ubuntu 16.04, the command `./sage -t -p --all --long > --optional=sage,optional,external` finishes with: > > -- > sage -t --lo

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

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 # 1 doctest failed

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

The first run of make gave the following error with gfan: Found local metadata for gfan-0.6.2.p0 Traceback (most recent call last): File "/home/slabbe/GitBox/sage/build/bin/sage-download-file", line 25, in import sage_bootstrap File

### [sage-release] Re: Sage 8.4.beta1 released

Running Ubuntu 16.06, I get Using --optional=bliss,cbc,ccache,cmake,dot2tex,external,gmpy2,lrslib,mpir,notedown,pandoc_attributes,python2,rst2ipynb,sage the command ./sage -t -p --all --long --optional=sage,optional,external --show-skipped --logfile=logs/ptestallshowskipped.log gives:

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

> this is a typical symptom of trying to link a wrong version of libpng. > Yes, but why does the `sage -f libpng` was not forced since it was necessary? I am not an expert at all on this, but from my point of view, it is like if there was problem with dependencies of giac. > > But what

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

> ... still running. > > make ptestlong eventually finished with: -- All tests passed! -- -- You received this message because you are subscribed to the

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

On Ubuntu 16.04, my first attempt at running make finishes with a problem with giac (undefined reference to `png_set_longjmp_fn') The log finishes with: ... [giac-1.4.9.45.p2] libtool: link: g++ -g -O2 -fno-strict-aliasing -DGIAC_GENERIC_CONSTANTS -Wl,-rpath

### [sage-release] Re: Sage 8.5.beta0 released

Using the following optional/external tags: --optional=bliss,cbc,ccache,cmake,dot2tex,external,gmpy2,lrslib,memlimit,mpir,notedown,pandoc_attributes,python2,rst2ipynb,sage External software detected for doctesting: ffmpeg,graphviz,gurobi,imagemagick,internet,latex,pandoc sage -tp

### [sage-release] Re: Sage 8.4.rc0 released

Running optional and external doctests: Using --optional=bliss,cbc,ccache,cmake,dot2tex,external,gmpy2,lrslib,memlimit,mpir,notedown,pandoc_attributes,python2,rst2ipynb,sage External software detected for doctesting: ffmpeg,graphviz,gurobi,imagemagick,internet,latex,pandoc I get:

### [sage-release] Re: Sage 8.4.beta6 released

The command: ./sage -t -p --all --long --optional=sage,optional,external Using --optional=bliss,cbc,ccache,cmake,dot2tex,external,gmpy2,lrslib,memlimit,mpir,notedown,pandoc_attributes,python2,rst2ipynb,sage External software detected for doctesting:

### [sage-release] Re: Sage 8.5.rc0 released

On Ubuntu 16.04, the command sage -t --all --optional=sage,optional,external tests the following optional and external doctests: Using --optional=bliss,cbc,ccache,cmake,dot2tex,external,gmpy2,lrslib,memlimit,mpir,normaliz,notedown,pandoc_attributes,pycosat,pynormaliz,python2,rst2ipynb,sage

### Re: [sage-release] Re: Sage 8.5.beta5 released

On Wednesday, November 28, 2018 at 9:49:53 AM UTC+1, François Bissey wrote: > > That’s interesting. I thought the failures in sage/databases/sql_db.py in > sage-on-gentoo > were due to the use of a newer version of sqlite. But if you see it too > that must be something > more subtle. > > I

### [sage-release] Re: Sage 8.5.beta5 released

On Ubuntu 16.04, the command sage -t --all --optional=sage,optional,external tests the following optional and external doctests: Using --optional=bliss,cbc,ccache,cmake,dot2tex,external,gmpy2,lrslib,memlimit,mpir,normaliz,notedown,pandoc_attributes,pycosat,pynormaliz,python2,rst2ipynb,sage

### [sage-release] Re: Sage 8.5.beta4 released

On Ubuntu 16.04, the command sage -t --all --optional=sage,optional,external tests the following optional and external doctests: Using --optional=bliss,cbc,ccache,cmake,dot2tex,external,gmpy2,lrslib,memlimit,mpir,normaliz,notedown,pandoc_attributes,pycosat,pynormaliz,python2,rst2ipynb,sage

### [sage-release] Re: Sage 8.6.rc0 released

Running tests on Ubuntu 16.04, with --optional=sage,optional,external, I get Using --optional=bliss,cbc,ccache,cmake,dot2tex,external,gmpy2,lrslib,memlimit,mpir,normaliz,notedown,pandoc_attributes,pycosat,pynormaliz,python2,rst2ipynb,sage External software detected for doctesting:

### [sage-release] Re: Sage 8.6.beta0 released

WIth Ubuntu 16.04, Runing test with --optional=sage,optional,external, I get Using --optional=bliss,cbc,ccache,cmake,dot2tex,external,gmpy2,lrslib,memlimit,mpir,normaliz,notedown,pandoc_attributes,pycosat,pynormaliz,python2,rst2ipynb,sage External software detected for doctesting:

### [sage-release] Re: Sage 8.6.beta1 released

With Ubuntu 16.04, running sage -t --optional=sage,optional,external --all I get Using --optional=bliss,cbc,ccache,cmake,dot2tex,external,gmpy2,lrslib,memlimit,mpir,normaliz,notedown,pandoc_attributes,pycosat,pynormaliz,python2,rst2ipynb,sage External software detected for doctesting:

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

Running make ptestlong with optional/external doctests, I get: Using --optional=bliss,cbc,ccache,cmake,cryptominisat,dot2tex,external,glucose,gmpy2,lrslib,memlimit,mpir,normaliz,notedown,pandoc_attributes,pycosat,pynormaliz,python2,rst2ipynb,sage External software detected for doctesting:

### [sage-release] Re: Sage 8.7.beta4 released

Using --optional=bliss,cbc,ccache,cmake,cryptominisat,dot2tex,external,glucose,gmpy2,lrslib,memlimit,mpir,normaliz,notedown,pandoc_attributes,pycosat,pynormaliz,python2,rst2ipynb,sage External software detected for doctesting: ffmpeg,graphviz,gurobi,imagemagick,internet,latex,pandoc I get:

### [sage-release] Re: Sage 8.7.beta6 released

Testing with --optional=sage,optional,external with Using --optional=bliss,cbc,ccache,cmake,cryptominisat,dot2tex,external,glucose,lrslib,memlimit,mpir,normaliz,notedown,pandoc_attributes,pycosat,pynormaliz,python2,rst2ipynb,sage External software detected for doctesting:

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

Running test with --optional=sage,optional,external I get External software detected for doctesting: ffmpeg,graphviz,gurobi,imagemagick,internet,latex,pandoc boolean_polynomial failure is not reproducable Using

### [sage-release] Re: Sage 8.7.beta7 released

Running tests on few optional + external packages, I get: -- sage -t --long src/sage/sat/boolean_polynomials.py # 1 doctest failed sage -t --long src/sage/combinat/designs/ext_rep.py # 1 doctest failed sage -t --long

### [sage-release] Re: Sage 8.7.rc0 released

Runing ptestlong with --optional=sage,optional,external i.e. testing the following packages: Using

### [sage-release] Re: Sage 8.7.beta3 released

Runing ptestlong with --optional=sage,optional,external, I get Using --optional=bliss,cbc,ccache,cmake,cryptominisat,dot2tex,external,glucose,gmpy2,lrslib,memlimit,mpir,normaliz,notedown,pandoc_attributes,pycosat,pynormaliz,python2,rst2ipynb,sage External software detected for doctesting:

### [sage-release] Re: Sage 8.7.beta1 released

Running tests with few optional and external doctests, I get: Using --optional=bliss,cbc,ccache,cmake,cryptominisat,dot2tex,external,glucose,gmpy2,lrslib,memlimit,mpir,normaliz,notedown,pandoc_attributes,pycosat,pynormaliz,python2,rst2ipynb,sage External software detected for doctesting:

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

I did not run any make test yet, but if I try to create a new notebook in Jupyter I get an error page saying "500 : Internal Server Error" and the error being printed in the terminal says ImportError: No module named defusedxml It is copied below: [I 09:59:24.941 NotebookApp] Creating

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

On Thursday, January 24, 2019 at 10:03:07 AM UTC+1, Sébastien Labbé wrote: > > I did not run any make test yet, but if I try to create a new notebook in > Jupyter I get an error page saying "500 : Internal Server Error" and the > error being printed in the terminal sa

### [sage-release] Re: Sage 8.7.beta2 relased

Runing tests with --optional=sage,optional,external, I get: Using --optional=bliss,cbc,ccache,cmake,cryptominisat,dot2tex,external,glucose,gmpy2,lrslib,memlimit,mpir,normaliz,notedown,pandoc_attributes,pycosat,pynormaliz,python2,rst2ipynb,sage External software detected for doctesting:

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

Now that I managed to installed pynormaliz, I could run the doctests including the below optional/external ones: Using

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

On another machine (on which I did not updated sage since a long time), I get trouble with documentation: [dochtml] OSError: /home/slabbe/GitBox/sage/local/lib/python2.7/site-packages/sage/graphs/generic_graph.py:docstring of sage.graphs.generic_graph.GenericGraph.longest_path:72: WARNING:

### [sage-release] Re: Sage 8.8.beta7 released

After fixing the pynormaliz issue myself, I may run optional and external doctests, and I get: -- sage -t --long src/sage/combinat/designs/ext_rep.py # 1 doctest failed sage -t --long src/sage/databases/findstat.py # 8

### [sage-release] Re: Sage 8.8.rc0 released

Testing the following optional and external packages: External software detected for doctesting: ffmpeg,graphviz,gurobi,imagemagick,internet,latex,pandoc Using

### [sage-release] Re: Sage 8.8.beta5 released

Runing optional/external doctests, more specifically with the following ones: Using

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

My first try at installing finishes with an error installing the (optional?) package pynormaliz *** Error building Sage. The following package(s) may have failed to build (not necessarily during this run of 'make all-start'): *

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

On Thursday, May 23, 2019 at 9:15:44 PM UTC+2, vdelecroix wrote: > > 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. > I am answering here: https://trac.sagemath.org/ticket/27731#comment:27 --

### [sage-release] Re: Sage 8.8.beta5 released

2 items had failures: >3 of 5 in > sage.databases.findstat.FindStatStatistic.generating_functions >2 of 4 in sage.databases.findstat.FindStatStatistic.oeis_search > 7 webbrowser tests not run > 0 tests not run because we ran out of time > [249 tests, 5 failures, 54.68 s]

### [sage-release] Re: Sage 8.8.beta4 released

On Ubuntu 16.04, upgrading to most recent sage develop as usual, I can't get the documentation to build. I can reproduce the issue after make doc-clean. It stops at ... [dochtml] installing. Log file: logs/dochtml.log [dochtml] error installing, exit status 1. Log file: logs/dochtml.log

### [sage-release] Re: Sage 8.8.beta4 released

> > > -- > sage -t --long src/sage/databases/oeis.py # 6 doctests failed > sage -t --long src/sage/symbolic/integration/external.py # 1 doctest > failed > sage -t --long src/sage/misc/package.py # 2 doctests failed > sage -t

### [sage-release] Re: Sage 8.8.beta4 released

Running tests with several optional and external packages, I get: Using

### [sage-release] Re: Sage 8..8 released

Sorry for the late report on 8.8, but it may be useful for comparison between releases. Testing the following optional and external packages External software detected for doctesting: ffmpeg,graphviz,gurobi,imagemagick,internet,latex,pandoc Using

### [sage-release] Re: Sage 8.8.beta3 released

Running tests with optional=sage,optional,external I get Using --optional=4ti2,bliss,cbc,ccache,cmake,cryptominisat,dot2tex,external,glucose,latte_int,lidia,lrslib,memlimit,mpir,ninja_build,normaliz,notedown,pandoc_attributes,pycosat,pynormaliz,python2,qhull,rst2ipynb,sage,topcom External

### Re: [sage-release] Re: Sage 8.9.beta7 released

On Friday, August 23, 2019 at 6:12:14 PM UTC+2, Sébastien Labbé wrote: > > > > On Friday, August 23, 2019 at 3:12:54 PM UTC+2, Eric Gourgoulhon wrote: >> >> Hello Sebastien, >> >> This works for me on Ubuntu 18.04, with both Python 2 and 3 versions of &g

### Re: [sage-release] Re: Sage 8.9.beta7 released

> It does not work. I will try rebuilding from scratch... > After rebuilding from scratch from a git clone, the SSL problem disapeared: ┌┐ │ SageMath version 8.9.beta8, Release Date: 2019-08-25 │ │ Using Python

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

On Sage 8.9.beta8, running optional and external tests Using --optional=awali,cbc,cryptominisat,dot2tex,e_antic,external,glucose,memlimit,normaliz,notedown,openssl,pandoc_attributes,pycosat,pynormaliz,python2,rst2ipynb,sage I get: