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

This also happened to me a few weeks ago. The underlying problem seems to be that the uninstall script fails because it tries to call sage-dist-helpers, but cannot find it. This file has recently been moved from src/bin to build/bin, which the uninstall script cannot know about. Once upgraded

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

The package fflas_ffpack-2.4.3 added in #26932 fails to compile for me on CentOS 7.6.1810, due to several errors of this form: g++: error: unrecognized command line option '-mavx512f' g++: error: unrecognized command line option '-mavx512vl' g++: error: unrecognized command line option

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

Thank you for the quick replies. It is the system's default compiler – no idea why it is so old. export FFLAS_FFPACK_CONFIGURE="-disable-fma -disable-fma4 -disable-avx > -disable-avx2" Hm, that did not work, giving still the same error for fflas-ffpack. I assume I would have to disable AVX

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

> > It would have been nice to have the config log from when you had the > failure. > Would you still like to have it? I could reproduce it I suppose. -- You received this message because you are subscribed to the Google Groups "sage-release" group. To unsubscribe from this group and stop

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

Oh, my bad. Here it is. Am Dienstag, 6. August 2019 07:34:02 UTC+2 schrieb François Bissey: > > I meant the config.log of fflas-ffpack not sage’s one. > > > On 6/08/2019, at 5:31 PM, Markus Wageringel > wrote: > > > > > > -- You received thi

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

Whenever I run `./sage -b` with Python 2, the extensions 'sage.matrix.matrix_mod2_dense' and 'sage.modules.vector_mod2_dense' get recompiled, even if nothing has changed. Apparently, this already happened with 8.8 though, but not with Python 3. -- You received this message because you are

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

With Python 3 on CentOS, all tests from ptestlong passed. With Python 2, I got a (transient) timeout in src/sage/parallel/map_reduce.py There seems to be a race condition. It is difficult for me to reproduce. Has anyone seen this before? I am unsure whether this might have been caused by

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

With 9.1.beta2, I frequently see the following transient failure on my patchbot running on CentOS 7.7: File

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

For now, `./bootstrap -D` can be used as a workaround for this problem. Am Dienstag, 14. Januar 2020 12:24:57 UTC+1 schrieb Dima Pasechnik: > > On Tue, Jan 14, 2020 at 10:57 AM chris wuthrich > > wrote: > > > > > > > > make build after pulling 9.1.beta0 produces an error below. I have no >

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

This may in part be due to #28744 which was merged in beta8. Before that, the Octave interface was so broken with Python 3 that even the detection of Octave failed, so these `external` doctests would never run during ptestalllong. Now, all Octave tests pass on my end, but I still have Octave

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

I also see the error in rings/integer.pyx again now. This is https://trac.sagemath.org/ticket/28106. The doctests are limited to 3300 MB of memory be default, but this test exceeds it. The limit can be manually increased using the `--memlimit` option. Am Dienstag, 31. März 2020 19:40:19 UTC+2

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

Since this beta, I get the following permanent failure: sage -t --long src/sage/env.py ** File "src/sage/env.py", line 15, in sage.env Failed example: out == repr((SAGE_ROOT, SAGE_LOCAL))

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

> Am 31.03.2020 um 23:30 schrieb Matthias Köppe : > Looks like this new doctest (from https://trac.sagemath.org/ticket/29287) > needs some os.path.abspath in it. Please open a ticket for this. Ok, I have opened https://trac.sagemath.org/ticket/29446 for

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

> Am 31.03.2020 um 23:25 schrieb Matthias Köppe : > > That is, the file `local/bin/sage-starts` is not found. This is with CentOS > 7.7. > > > This script was moved in https://trac.sagemath.org/ticket/23769 > It looks like the patchbot needs to be

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

With a clean build on Ubuntu 20.04, ptestlong passes, but Jupyter does not start anymore due to an SSL problem, using Sage's Python 3. (The system Python 3.8 is not picked up because of missing dependencies sqlite and xz, but that is ok.) $ ./sage -n jupyter Please wait while the Sage

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

> Am 11.09.2020 um 20:46 schrieb Samuel Lelièvre : > > On Debian or Debian-based system like Ubuntu, check whether > libssl-dev is installed with this command (sudo not needed): > ``` > $ dpkg-query --list libssl-dev > ``` Thank you for the explanations. The command returns: $ dpkg-query

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

> Am 11.09.2020 um 20:17 schrieb Matthias Köppe : > > Is "libssl-dev" installed? (see build/pkgs/openssl/distros/debian.txt) It looks like it is not: $ ldconfig -p | grep ssl libxmlsec1-openssl.so.1 (libc6,x86-64) => /lib/x86_64-linux-gnu/libxmlsec1-openssl.so.1

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

With Neovim as editor, the same warning appears in its builtin terminal, followed by some error messages that break the REPL. Luckily, upgrading Neovim from 0.2.2 to 0.4.3 fixed it on my end. emanuel.c...@gmail.com schrieb am Dienstag, 11. August 2020 um 17:39:29 UTC+2: > Damn ! > > This

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

ption. > Am 22.08.2020 um 06:12 schrieb John H Palmieri : > > > > On Friday, August 21, 2020 at 1:37:21 PM UTC-7, Markus Wageringel wrote: > With Neovim as editor, the same warning appears in its builtin terminal, > followed by some error messages that break the REPL. Lu

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

This is caused by the changes to symbolic functions in ticket #31047 and also affects the Mathematica interface. I have opened https://trac.sagemath.org/ticket/31756 for it. Sébastien Labbé schrieb am Donnerstag, 25. März 2021 um 12:29:29 UTC+1: > sage -t --long --warn-long 79.7

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

I have also seen this error, but it disappeared after a distclean. tdumont schrieb am Freitag, 14. Januar 2022 um 14:18:30 UTC+1: > > Upgrading to 9.5rc1 on Ubuntu 21-10: > > - compilation ok. > > - make ptestlong: > ERRORS >

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

Instead of modifying the .gitattributes file, you could try adding it to .git/info/attributes which is local to your repository. tsc...@ucdavis.edu schrieb am Samstag, 12. Februar 2022 um 01:37:40 UTC+1: > Something that has come up a few times when doing these upgrades for me > has been line