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

[Samuel Lelievre]

Le mardi 18 janvier 2022 à 02:37:20 UTC, Marc Culler on sage-release:

> That worked like a charm!
>
>   * frame #0: 0x83c0f9024900
> frame #1: 0x000153ff8b7c 
> _dop.cpython-39-darwin.so`PyFortranObject_New 
> + 40
> frame #2: 0x000153ff66fc _dop.cpython-39-darwin.so`PyInit__dop + 
> 1020
>
> [...]
>
> If anyone knows what dop stands for, I am all ears.
>

It seems "DOP" or "DOPRI" or "RKDP" stand for "Dormand & Prince"
or "Runge-Kutta-Dormand-Prince" and refer to a method, or family
of methods (of the Runge-Kutta family), devised  by these authors
for numerically solving ordinary differential equations.

See:

https://en.wikipedia.org/wiki/Dormand–Prince_method
https://docs.scipy.org/doc/scipy/reference/generated/scipy.integrate.DOP853.html
http://www.unige.ch/~hairer/prog/nonstiff/dop853.f

In particular, the file "dop853.f", linked to above, states  "DOP853"
is "an explicit Runge-Kutta method of order 8(5,3) due to Dormand
& Prince (with stepsize control and dense output)".

These abbreviation seem common in the world of numerical methods
for solving ordinary differential equations but so far that meaning
of DOP is missing from the wikipedia disambiguation page

https://en.wikipedia.org/wiki/DOP

-- 
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 discussion on the web visit 
https://groups.google.com/d/msgid/sage-release/8ff24293-3a80-4d65-9275-46ed122a2950n%40googlegroups.com.

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

[Samuel Lelievre]

2022-01-24 21:20 UTC, Volker Braun on sage-release:
>
> 97d550d15c (tag: 9.5.rc4, trac/develop) Updated SageMath version to 
9.5.rc4

On Debian 10 buster, occasional `sagemath_doc_html` failure,
tracked at

- Sage Trac ticket 33139
Fix sagemath_doc_html-none build failure
https://trac.sagemath.org/ticket/33139

On that platform, `make doc-clean doc-uninstall`
or `make distclean` allow to get past that failure:
a subsequent `make` succeeds.

After that, testing with `make -s V=0 ptestlong` fails on two files:
```
... src/sage/features/interfaces.py # Timed out
... src/sage/game_theory/parser.py # 2 doctests failed
```

I opened ticket #33248 for the timeout:

- Fix timeout in feature test for Mathematica
  https://trac.sagemath.org/ticket/33248

and there is already a positively reviewed ticket about
the `game_theory/parser.py` failed doctests:

- lrslib: fix doctest in game_theory/parser.py
  https://trac.sagemath.org/ticket/33101

-- 
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 discussion on the web visit 
https://groups.google.com/d/msgid/sage-release/6c3e5cc1-718c-4f8e-ae68-24da6d53ddb0n%40googlegroups.com.

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

[Samuel Lelievre]

Fixing links in my previous post, thanks Frédéric's tip at
https://groups.google.com/g/sage-devel/c/t3ZRCJ5coPU/m/6AJxsCxfBQAJ


2022-01-23 à 17:57:38 UTC, Samuel Lelièvre a écrit :

> 2022-01-22 13:05:04 UTC, Samuel Lelièvre on sage-release:
>
>>
>> On Cygwin: failed to build sagemath_doc_html. 
>>
>> On Debian: failed to build sagemath_doc_html. 
>> See the ticket 0 patchbot report for pascaline at 
>> https://patchbot.sagemath.org/ticket/0/
>
>
 That's the earlier of two pascaline reports at

https://patchbot.sagemath.org/ticket/0/?base=9.5.rc3
 

> On Debian (but not on Cygwin), running `make distclean`
> and then `make` again allowed `sagemath_doc_html`
> to build and the whole build to complete.
>
> Tests then timed out in two files:
>
> - `src/sage/features/interfaces.py`
> - `src/sage/coding/linear_code.py`
>
> and failed in one file
>
> - `src/sage/game_theory/parser.py`
>
> The test failures in that file are due to lrslib doctests,
> fixed in #33101 which already has positive review.
> Not sure about the timeouts, maybe they also have
> to do with feature detection.
>
> See the second pascaline report at
>
> https://patchbot.sagemath.org/ticket/0/
>

That's the latest of two pascaline reports at

https://patchbot.sagemath.org/ticket/0/?base=9.5.rc3

-- 
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 discussion on the web visit 
https://groups.google.com/d/msgid/sage-release/240ec07e-d263-45b0-b2a4-dca1a2c9e047n%40googlegroups.com.

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

[Samuel Lelievre]

2022-01-19 00:05:13 UTC, Volker Braun on sage-release:
>
> 8ea92d580a (tag: 9.5.rc3, trac/develop) Updated SageMath version to 
9.5.rc3

On Ubuntu 21.10, the build succeeded but 5 doctests
failed in `src/sage/modules/free_module_integer.py`.

I don't know whether that failure is already tracked.
Can anybody point to an existing ticket? Otherwise
I can open one.  Details below.   --Samuel

-

Failure summary:
```
$ make -s V=0 testlong
...
--
sage -t --long --warn-long 127.1 
--random-seed=243861417107614574365038834487998971463 
src/sage/modules/free_module_integer.py  # 5 doctests failed
--
Total time for all tests: 11153.8 seconds
cpu time: 9705.7 seconds
cumulative wall time: 10720.0 seconds
Features detected for doctesting: 
4ti2,dvipng,ffmpeg,graphviz,imagemagick,lrslib,pandoc,pdf2svg,sage.combinat,sage.geometry.polyhedron,sage.graphs,sage.plot,sage.rings.number_field,sage.rings.real_double,sage.symbolic,sagemath_doc_html,sphinx
Pytest is not installed, skip checking tests that rely on it.
make: *** [Makefile:242: testlong] Error 1
```

The failure persists when testing that file again.

```
$ SEED=243861417107614574365038834487998971463
$ alias sagetest="./sage -t --long --warn-long 128 --random-seed=$SEED"
$ sagetest src/sage/modules/free_module_integer.py  # 5 doctests failed
Running doctests with ID 2022-01-23-22-42-46-e3b619c7.
Git branch: develop
Using --optional=build,debian,pip,sage,sage_spkg
Features to be detected: 
4ti2,benzene,bliss,buckygen,conway_polynomials,csdp,database_cremona_ellcurve,database_cremona_mini_ellcurve,database_jones_numfield,database_knotinfo,dvipng,ffmpeg,graphviz,imagemagick,jupymake,kenzo,latte_int,lrslib,mcqd,meataxe,pandoc,pdf2svg,plantri,pynormaliz,rubiks,sage.combinat,sage.geometry.polyhedron,sage.graphs,sage.plot,sage.rings.number_field,sage.rings.real_double,sage.symbolic,sage_numerical_backends_coin,sagemath_doc_html,sphinx,tdlib
Doctesting 1 file.
sage -t --long --warn-long 128.0 
--random-seed=243861417107614574365038834487998971463 
src/sage/modules/free_module_integer.py
**
File "src/sage/modules/free_module_integer.py", line 213, in 
sage.modules.free_module_integer.FreeModule_submodule_with_basis_integer
Failed example:
L.shortest_vector()
Exception raised:
Traceback (most recent call last):
  File "sage/misc/cachefunc.pyx", line 1943, in 
sage.misc.cachefunc.CachedMethodCaller.__call__ 
(build/cythonized/sage/misc/cachefunc.c:10347)
return cache[k]
KeyError: ((True, 'fplll'), ())

During handling of the above exception, another exception occurred:

Traceback (most recent call last):
  File 
"/opt/s/sage-9-5-c3-fresh-clone/local/var/lib/sage/venv-python3.9/lib/python3.9/site-packages/sage/doctest/forker.py",
 
line 694, in _run
self.compile_and_execute(example, compiler, test.globs)
  File 
"/opt/s/sage-9-5-c3-fresh-clone/local/var/lib/sage/venv-python3.9/lib/python3.9/site-packages/sage/doctest/forker.py",
 
line 1088, in compile_and_execute
exec(compiled, globs)
  File "", 
line 1, in 
L.shortest_vector()
  File "sage/misc/cachefunc.pyx", line 1948, in 
sage.misc.cachefunc.CachedMethodCaller.__call__ 
(build/cythonized/sage/misc/cachefunc.c:10483)
w = self._instance_call(*args, **kwds)
  File "sage/misc/cachefunc.pyx", line 1824, in 
sage.misc.cachefunc.CachedMethodCaller._instance_call 
(build/cythonized/sage/misc/cachefunc.c:9949)
return self.f(self._instance, *args, **kwds)
  File 
"/opt/s/sage-9-5-c3-fresh-clone/local/var/lib/sage/venv-python3.9/lib/python3.9/site-packages/sage/modules/free_module_integer.py",
 
line 591, in shortest_vector
w = vector(ZZ, SVP.shortest_vector(L, *args, **kwds))
  File "src/fpylll/fplll/svpcvp.pyx", line 77, in 
fpylll.fplll.svpcvp.shortest_vector
  File "src/fpylll/fplll/bkz_param.pyx", line 269, in 
fpylll.fplll.bkz_param.load_strategies_json
RuntimeError: Aborted
**
File "src/sage/modules/free_module_integer.py", line 563, in 
sage.modules.free_module_integer.FreeModule_submodule_with_basis_integer.shortest_vector
Failed example:
L.shortest_vector().norm().n()
Exception raised:
Traceback (most recent call last):
  File "sage/misc/cachefunc.pyx", line 1943, in 
sage.misc.cachefunc.CachedMethodCaller.__call__ 
(build/cythonized/sage/misc/cachefunc.c:10347)
return cache[k]
KeyError: ((True, 'fplll'), ())

During handling of the above exception, another exception occurred:

Traceback (most recent call last):
  File 
"/opt/s/sage-9-5-c3-fresh-clone/local/var/lib/sage/venv-python3.9/lib/python3.9/site-packages/sage/doctest/forker.py",
 
line 694, in _run

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

[Samuel Lelievre]

2022-01-22 13:05:04 UTC, Samuel Lelievre on sage-release:

>
> On Cygwin: failed to build sagemath_doc_html. 
>
> On Debian: failed to build sagemath_doc_html. 
> See the ticket 0 patchbot report for pascaline at 
> https://patchbot.sagemath.org/ticket/0/


On Debian (but not on Cygwin), running `make distclean`
and then `make` again allowed `sagemath_doc_html`
to build and the whole build to complete.

Tests then timed out in two files:

- `src/sage/features/interfaces.py`
- `src/sage/coding/linear_code.py`

and failed in one file

- `src/sage/game_theory/parser.py`

The test failures in that file are due to lrslib doctests,
fixed in #33101 which already has positive review.
Not sure about the timeouts, maybe they also have
to do with feature detection.

See the second pascaline report at

https://patchbot.sagemath.org/ticket/0/

(for as long as that page is about Sage 9.5.rc3 ---
not sure how to refer to that report longer term).

-- 
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 discussion on the web visit 
https://groups.google.com/d/msgid/sage-release/8ba92fb5-6f9d-4e29-8266-99d30f387256n%40googlegroups.com.

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

[Samuel Lelievre]

Thanks Dima and Matthias for your feedback.
I opened three tickets related to my report:

- #33078: Use system Python 3 on Cygwin
- #33079: Fix python3 build failure on Cygwin
- #33080: Fix scipy-3.7.2 build failure on Cygwin

Tried applying #33055, which did not seem to help
with the Python 3 issues on Cygwin.   --Samuel

-- 
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 discussion on the web visit 
https://groups.google.com/d/msgid/sage-release/f189fcaf-0cd0-4ada-8228-158e526dc3adn%40googlegroups.com.

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

[Samuel Lelievre]

2021-10-30 18:34:21 UTC, Emmanuel Charpentier:
>
> After rebuilding and reinstalling the same (really)
> optional packages, `ptestlong` gets exactly one
> (reproducible) failure, i. e. the one reported by
> Samuel Lelièvre.
>
> I am at loss as to why I needed to rebuild 9.5
> from sratch instead of upgrading from 9.3. Ideas?

I'm sure you mean: "why I needed to rebuild 9.5.beta5
from scratch instead of upgrading from 9.5.beta3".

Not sure why a distclean was needed in that case.

-- 
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 discussion on the web visit 
https://groups.google.com/d/msgid/sage-release/422c4441-dfb2-4b97-85d6-7f706a2be402n%40googlegroups.com.

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

[Samuel Lelievre]

2021-09-14 22:50:30 UTC, Volker Braun:

>
> c349c87d0d (tag: 9.5.beta1, trac/develop) Updated SageMath version to 
> 9.5.beta1
>

Thanks for this new release.

In Cygwin 3.2.0 in Windows 10:

```bash
$ export MAKE='make -j4' && ./bootstrap -q && ./configure -q && make -s V=0 
&& make -s V=0 ptestlong
...
--
sage -t --long --warn-long 251.2 --random-seed=0 src/sage/misc/persist.pyx  
# 1 doctest failed
--
Total time for all tests: 10096.3 seconds
cpu time: 32053.6 seconds
cumulative wall time: 59597.3 seconds
Pytest is not installed, skip checking tests that rely on it.
make: *** [Makefile:201: ptestlong] Error 1

$ ./sage -t --long -a --failed
Running doctests with ID 2021-09-22-10-35-59-a9965c51.
Git branch: develop
Using --optional=build,cygwin,dochtml,pip,sage,sage_spkg
Doctesting entire Sage library.
Only doctesting files that failed last test.
Doctesting 1 file.
sage -t --long --warn-long 278.3 --random-seed=0 src/sage/misc/persist.pyx
**
File "src/sage/misc/persist.pyx", line 1018, in sage.misc.persist.picklejar
Failed example:
if uid==0:
raise OSError('You must not run the doctests as root, geez!')
elif sys.platform == 'cygwin':
raise OSError("This won't always behave on Cygwin depending on 
permission handling configuration.")
else:
sage.misc.persist.picklejar(1, dir + '/noaccess')
Expected:
Traceback (most recent call last):
...
PermissionError: ...
Got:

Traceback (most recent call last):
  File 
"/home/s/sage9h/local/lib/python3.8/site-packages/sage/doctest/forker.py", 
line 704, in _run
self.compile_and_execute(example, compiler, test.globs)
  File 
"/home/s/sage9h/local/lib/python3.8/site-packages/sage/doctest/forker.py", 
line 1098, in compile_and_execute
exec(compiled, globs)
  File "", line 4, in 
raise OSError("This won't always behave on Cygwin depending on 
permission handling configuration.")
OSError: This won't always behave on Cygwin depending on permission 
handling configuration.
**
1 item had failures:
   1 of  10 in sage.misc.persist.picklejar
[139 tests, 1 failure, 11.17 s]
--
sage -t --long --warn-long 278.3 --random-seed=0 src/sage/misc/persist.pyx  
# 1 doctest failed
--
Total time for all tests: 12.0 seconds
cpu time: 1.3 seconds
cumulative wall time: 11.2 seconds
Pytest is not installed, skip checking tests that rely on it.
```

That failure is already addressed at:

  Sage Trac ticket 32514
  Fix file permission doctest in src/sage/misc/persist.pyx
  https://trac.sagemath.org/ticket/32514

so hopefully the next beta can pass all tests in Cygwin!  --Samuel

-- 
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 discussion on the web visit 
https://groups.google.com/d/msgid/sage-release/7f1b76b9-ac6f-4170-8991-98aae2e896a2n%40googlegroups.com.

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

[Samuel Lelievre]

Thanks for this new release!

On macOS 10.14.6 with many Homebrew packages installed,
starting from a working previous beta release,
Sage 9.4.beta6 builds and passes all but one doctests.

```
$ git pull origin develop --tags -q && git branch -v
* develop  8bae3ff7ad Updated SageMath version to 9.4.beta6
$ source .homebrew-build-env
$ ./bootstrap -q
$ ./configure -q
$ make -s V=0
$ make -s V=0 testlong
...
--
sage -t --long --random-seed=0 src/sage/geometry/polyhedron/base.py  # 1 
doctest failed
--
Total time for all tests: 15741.9 seconds
cpu time: 12528.9 seconds
cumulative wall time: 15317.8 seconds
Pytest is not installed, skip checking tests that rely on it.
make: *** [testlong] Error 1
```

Here is the test failure:

```
$ ./sage -t --long --random-seed=0 src/sage/geometry/polyhedron/base.py
Running doctests with ID 2021-07-25-13-39-10-94bfce9c.
Git branch: develop
Using 
--optional=build,dochtml,gap_packages,homebrew,libsemigroups,pip,sage,sage_spkg
Doctesting 1 file.
sage -t --long --warn-long 69.6 --random-seed=0 
src/sage/geometry/polyhedron/base.py
**
File "src/sage/geometry/polyhedron/base.py", line 6651, in 
sage.geometry.polyhedron.base.Polyhedron_base.face_lattice
Failed example:
n == get_memory_usage()
Expected:
True
Got:
False
**
1 item had failures:
   1 of  42 in sage.geometry.polyhedron.base.Polyhedron_base.face_lattice
[1758 tests, 1 failure, 100.97 s]
--
sage -t --long --warn-long 69.6 --random-seed=0 
src/sage/geometry/polyhedron/base.py  # 1 doctest failed
--
Total time for all tests: 101.6 seconds
cpu time: 54.0 seconds
cumulative wall time: 101.0 seconds
Pytest is not installed, skip checking tests that rely on it.
```

Possibly related to Singular, if it is the same failure as in
https://trac.sagemath.org/ticket/31623

I will try rebasing #32001 on Sage 9.4.beta6 to see
if upgrading to Singular 4.2.1 solves this problem.

-- 
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 discussion on the web visit 
https://groups.google.com/d/msgid/sage-release/ac099b54-b26a-4571-a66f-084549703c8fn%40googlegroups.com.

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

[Samuel Lelievre]

Thanks for this new release. Would a ticket upgrading
to the latest OpenSSL still be considered for Sage 9.3?

Or should we just strongly encourage users to install
OpenSSL via some package manager and build Sage
from source using that?

-- 
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 discussion on the web visit 
https://groups.google.com/d/msgid/sage-release/4eb78673-ec4e-4cb9-b0fc-a4107373ab28n%40googlegroups.com.

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

[Samuel Lelievre]

2021-02-08 02:11:22 UTC, Samuel Lelievre:
>
> On macOS 10.14.6 with lots of Homebrew packages, 
> [failed to build linbox]. Logs: 
>
> https://www.math.u-psud.fr/~lelievre/t/slel-2021-02-08-s93b7-brew.zip 
>
> I'll try #31355. 

Same failure to build linbox after applying #31355.
I'm sticking to Sage 9.3.beta5 for now. I should maybe
check if I can still build Sage 9.3.beta5. Or maybe try
removing a few Homebrew packages in case that helps.

-- 
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 discussion on the web visit 
https://groups.google.com/d/msgid/sage-release/515d3489-4c1b-47fd-b801-73c7c9676a07n%40googlegroups.com.

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

[Samuel Lelievre]

Sorry for the sloppy report without a config.log.

For the record, my workaround to the problem
was to use the brew-installed Jupyter + JupyterLab.
One can install the SageMath Jupyter kernel for it
quite easily. The following works on macOS
(to find out what to put for KERNELS, one can run
commands such as `jupyter kernelspec list`
or `jupyter --paths`):
```
$ SAGE_LOCAL=`sage -c 'print(SAGE_LOCAL)'`
$ SAGE_KERNEL=$SAGE_LOCAL/share/jupyter/kernels/sagemath 
$ KERNELS=$HOME/Library/Jupyter/kernels
$ ln -s $SAGE_KERNEL $KERNELS
```
Then instead of `sage -n jupyter` or `sage -n jupyterlab`,
Jupyter Notebook and JupyterLab can be launched
the "normal" (non-Sage-specific) way:
```
$ jupyter notebook
$ jupyter lab
```


Fri 2020-11-20 18:08:00 UTC, Matthias Köppe:
>
> Samuel, you didn't include config.log, but my guess
> is that it would reveal that you are not using python3
>  from system or homebrew. config.log contains the
> relevant information why the system python3 is
> rejected by Sage.
>
> Fri 2020-11-20 00:42:07 UTC Samuel Lelievre:
>>
>>
>> > From: Volker
>> > Subject: Sage 9.3.beta1 released
>> >
>> > 222059565b (tag: 9.3.beta1, trac/develop)
>> > Updated SageMath version to 9.3.beta1
>>
>> Thanks for this new release!
>>
>> All tests passed here when running  `make testlong`
>> (more detail below), but I could not install JupyterLab.

-- 
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 discussion on the web visit 
https://groups.google.com/d/msgid/sage-release/e86b4046-5b20-4b8e-8336-693cfafab769n%40googlegroups.com.

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

[Samuel Lelievre]

> From: Volker
> Subject: Sage 9.3.beta1 released
>
> 222059565b (tag: 9.3.beta1, trac/develop)
> Updated SageMath version to 9.3.beta1

Thanks for this new release!

All tests passed here when running  `make testlong`
(more detail below), but I could not install JupyterLab.

Setup

- macOS 10.14.6 Mojave
- many homebrew packages
- existing Sage installation previously at some 9.2.rcN

Commands

```
$ git pull origin develop -q
$ source .homebrew-build-env
$ MAKE='make -j1'
$ V=0
$ ./bootstrap -q
$ ./configure --enable-openssl -q
$ make -s V=0 && make -s V=0 testlong
...
All tests passed!
```

```
$ V=0 ./sage -i jupyterlab_widgets
...
[nodeenv] Requirement already satisfied: nodeenv~=1.4.0 in 
/opt/s/sage93b/local/lib/python3.8/site-packages (from -r 
/opt/s/sage93b/build/pkgs/nodeenv/requirements.txt (line 1)) (1.4.0)
make --no-print-directory nodejs-no-deps
cd '/opt/s/sage93b/build/pkgs/nodejs' && . 
'/opt/s/sage93b/src/bin/sage-env-config' && . 
'/opt/s/sage93b/src/bin/sage-env' && . 
'/opt/s/sage93b/build/bin/sage-build-env-config' && sage-logger -p 
'/opt/s/sage93b/build/pkgs/nodejs/spkg-install' 
'/opt/s/sage93b/logs/pkgs/nodejs-12.18.3.log'
[nodejs-12.18.3] Will use/install nodejs in nodeenv located at 
/opt/s/sage93b/local/share/nodejs/12.18.3 ...
[nodejs-12.18.3]  * Environment already exists: 
/opt/s/sage93b/local/share/nodejs/12.18.3
[nodejs-12.18.3]  * Install prebuilt node (12.18.3) .
[nodejs-12.18.3] Traceback (most recent call last):
[nodejs-12.18.3]   File 
"/opt/s/sage93b/local/lib/python3.8/urllib/request.py", line 1350, in 
do_open
[nodejs-12.18.3] h.request(req.get_method(), req.selector, req.data, 
headers,
[nodejs-12.18.3]   File 
"/opt/s/sage93b/local/lib/python3.8/http/client.py", line 1255, in request
[nodejs-12.18.3] self._send_request(method, url, body, headers, 
encode_chunked)
[nodejs-12.18.3]   File 
"/opt/s/sage93b/local/lib/python3.8/http/client.py", line 1301, in 
_send_request
[nodejs-12.18.3] self.endheaders(body, encode_chunked=encode_chunked)
[nodejs-12.18.3]   File 
"/opt/s/sage93b/local/lib/python3.8/http/client.py", line 1250, in 
endheaders
[nodejs-12.18.3] self._send_output(message_body, 
encode_chunked=encode_chunked)
[nodejs-12.18.3]   File 
"/opt/s/sage93b/local/lib/python3.8/http/client.py", line 1010, in 
_send_output
[nodejs-12.18.3] self.send(msg)
[nodejs-12.18.3]   File 
"/opt/s/sage93b/local/lib/python3.8/http/client.py", line 950, in send
[nodejs-12.18.3] self.connect()
[nodejs-12.18.3]   File 
"/opt/s/sage93b/local/lib/python3.8/http/client.py", line 1424, in connect
[nodejs-12.18.3] self.sock = self._context.wrap_socket(self.sock,
[nodejs-12.18.3]   File "/opt/s/sage93b/local/lib/python3.8/ssl.py", line 
500, in wrap_socket
[nodejs-12.18.3] return self.sslsocket_class._create(
[nodejs-12.18.3]   File "/opt/s/sage93b/local/lib/python3.8/ssl.py", line 
1040, in _create
[nodejs-12.18.3] self.do_handshake()
[nodejs-12.18.3]   File "/opt/s/sage93b/local/lib/python3.8/ssl.py", line 
1309, in do_handshake
[nodejs-12.18.3] self._sslobj.do_handshake()
[nodejs-12.18.3] ssl.SSLCertVerificationError: [SSL: 
CERTIFICATE_VERIFY_FAILED] certificate verify failed: unable to get local 
issuer certificate (_ssl.c:1123)
[nodejs-12.18.3]
[nodejs-12.18.3] During handling of the above exception, another exception 
occurred:
[nodejs-12.18.3]
[nodejs-12.18.3] Traceback (most recent call last):
[nodejs-12.18.3]   File "/opt/s/sage93b/local/bin/nodeenv", line 8, in 

[nodejs-12.18.3] sys.exit(main())
[nodejs-12.18.3]   File 
"/opt/s/sage93b/local/lib/python3.8/site-packages/nodeenv.py", line 1046, 
in main
[nodejs-12.18.3] create_environment(env_dir, opt)
[nodejs-12.18.3]   File 
"/opt/s/sage93b/local/lib/python3.8/site-packages/nodeenv.py", line 935, in 
create_environment
[nodejs-12.18.3] install_node(env_dir, src_dir, opt)
[nodejs-12.18.3]   File 
"/opt/s/sage93b/local/lib/python3.8/site-packages/nodeenv.py", line 700, in 
install_node
[nodejs-12.18.3] install_node_wrapped(env_dir, src_dir, opt)
[nodejs-12.18.3]   File 
"/opt/s/sage93b/local/lib/python3.8/site-packages/nodeenv.py", line 722, in 
install_node_wrapped
[nodejs-12.18.3] download_node_src(node_url, src_dir, opt)
[nodejs-12.18.3]   File 
"/opt/s/sage93b/local/lib/python3.8/site-packages/nodeenv.py", line 553, in 
download_node_src
[nodejs-12.18.3] dl_contents = io.BytesIO(urlopen(node_url).read())
[nodejs-12.18.3]   File 
"/opt/s/sage93b/local/lib/python3.8/site-packages/nodeenv.py", line 585, in 
urlopen
[nodejs-12.18.3] return urllib2.urlopen(req)
[nodejs-12.18.3]   File 
"/opt/s/sage93b/local/lib/python3.8/urllib/request.py", line 222, in urlopen
[nodejs-12.18.3] return opener.open(url, data, timeout)
[nodejs-12.18.3]   File 
"/opt/s/sage93b/local/lib/python3.8/urllib/request.py", line 525, in open
[nodejs-12.18.3] response = self._open(req, data)
[nodejs-12.18.3]   File 
"/opt/s/sage93b/local/lib/python3.8/urllib/request.py", line 

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

[Samuel Lelievre]

2020-11-03 09:57:12 UTC, Jonathan:
>
> There no windows binaries for 9.2 yet. Maybe there
>
is a reason for it, but I should wanted to post that.
>
 
It's being worked on. It's not unusual that preparing Windows binaries
for a new Sage version takes a few days to a few weeks.

New releases of the Sage-Windows installer appear at

https://github.com/sagemath/sage-windows/releases/

If you sign up to GitHub, you can get an alert in the form of
an email from GitHub every time a new version is released.

For that, use the "Watch..." button after signing in to GitHub.
More precisely, select "Watch > Releases only".

-- 
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 discussion on the web visit 
https://groups.google.com/d/msgid/sage-release/248c94c6-1b09-4fb7-9521-94e64ffea9c0o%40googlegroups.com.

[sage-release] Re: info

[Samuel Lelievre]

Le samedi 24 octobre 2020 10:13:29 UTC+2, HG a écrit:
>
> Yesterday no one pip version worked ? I am on ubuntu 20.10
> which should get out in few days, I did a do-release-upgrade -d
>
> This morning I was trying pip : 
>
> $ sudo -H pip3 install sage
> Requirement already satisfied: sage in
> /usr/lib/python3/dist-packages (9.2b12) 
>
> I installed sagemath as a deb package. I wonder if sage
> can be installed with pip3 (I don't want to try because
> I don't want to lose my config).
> Does somebody know about this ? 
>
> Last week I compiled last rc release I didn't have any
> problem. I deleted it because it's a big release. 
>
> Best
> Henri

Making Sage pip-installable is work in progress, tracked at:

https://trac.sagemath.org/ticket/21507

-- 
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 discussion on the web visit 
https://groups.google.com/d/msgid/sage-release/f11dd8c4-4f0b-4ca3-be18-ef1df57f5236o%40googlegroups.com.

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

[Samuel Lelievre]

Volker Braun wrote:
>
> f6250c2682 (tag: 9.2.rc0, trac/develop) Updated SageMath version to 
9.2.rc0


Thanks for this new release! I tried this:

- Sage 9.2.rc0 + #30589 (Use Python 3.9.0)

on two systems:

- Debian 10 buster
- macOS 10.14.6 Mojave with Homebrew

Things look good. Only two failures, as expected, see

- #30184 (Support Python 3.9)

Are there are already tickets for these?

See further down for the exact commands I ran.

Quality of life is improved with the ability to run bootstrap
in quiet mode, since #30533 and #30664 were merged;
many thanks to Michael Orlitzky and Matthias Koeppe.

I hope it can be even further improved, see below.


## Quality of life tickets

- "make distclean" should not run "./configure"
  https://trac.sagemath.org/ticket/29310

  needs branch

- Have configure run quiet if started by make in silent mode
  https://trac.sagemath.org/ticket/30258

  needs branch

- make V=0: Suppress "make --no-print-directory" lines for package builds
  https://trac.sagemath.org/ticket/30541

  needs branch

- Improve configure's recommendation message
  https://trac.sagemath.org/ticket/30624#comment:3

  needs work


## Debian 10 buster

>From an existing installation on Debian 10 buster.

Apply 50389
```
$ git trac checkout 50389
```

Check we are based on 9.2.rc0
```
$ git log --oneline -3
6d3a0fa824 (HEAD -> t/30589/upgrade-python-3.9, 
trac/u/mkoeppe/upgrade-python-3.9) build/pkgs/python3: Update to 3.9.0
255d22ba66 build/pkgs/python3: Update to 3.9.0rc2
f6250c2682 (tag: 9.2.rc0, origin/develop, origin/HEAD, develop) Updated 
SageMath version to 9.2.rc0
```

Run make distclean, boostrap, configure, make, make testlong:
```
$ V=0 ; \
  MAKE='make -j1' ; \
  make -s V=0 distclean \
  &&  ./bootstrap \
  &&  ./configure --without-system-python 
--enable-download-from-upstream-url -q \
  &&  make -s V=0 \
  &&  make -s V=0 testlong
...
--
sage -t --long --random-seed=0 src/sage/functions/other.py  # 1 doctest 
failed
sage -t --long --random-seed=0 
src/sage/rings/polynomial/pbori/randompoly.py  # 1 doctest failed
--
Total time for all tests: 13876.9 seconds
cpu time: 12377.7 seconds
cumulative wall time: 13454.8 seconds
```


## macOS 10.14.6 Mojave

>From an existing installation on macOS 10.14.6 Mojave.

Apply 50389
```
$ git trac checkout 50389
```

Check we are based on 9.2.rc0
```
$ git log --oneline -3
6d3a0fa824 (HEAD -> t/30589/upgrade-python-3.9, 
trac/u/mkoeppe/upgrade-python-3.9) build/pkgs/python3: Update to 3.9.0
255d22ba66 build/pkgs/python3: Update to 3.9.0rc2
f6250c2682 (tag: 9.2.rc0, origin/develop, develop) Updated SageMath version 
to 9.2.rc0
```

Run make distclean, apply homebrew build env, boostrap, configure, make, 
make testlong:
```
$ V=0 ; \
  MAKE='make -j1' ; \
  make -s V=0 distclean \
  &&  source .homebrew-build-env
  &&  ./bootstrap \
  &&  ./configure --without-system-python 
--enable-download-from-upstream-url -q \
  &&  make -s V=0 \
  &&  make -s V=0 testlong
...
--
sage -t --long --warn-long 123.3 --random-seed=0 
src/sage/functions/other.py  # 1 doctest failed
sage -t --long --warn-long 123.3 --random-seed=0 
src/sage/rings/polynomial/pbori/randompoly.py  # 1 doctest failed
--
Total time for all tests: 22359.6 seconds
cpu time: 16438.8 seconds
cumulative wall time: 21763.6 seconds
make: *** [testlong] Error 1
```

-- 
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 discussion on the web visit 
https://groups.google.com/d/msgid/sage-release/15c55df0-0c6f-48f5-9f2f-19b32cd0c9f5o%40googlegroups.com.

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

[Samuel Lelievre]

2020-09-21 09:23:54 UTC, Samuel Lelievre:
>
>
> This is now:
>
> - Sage Trac ticket 30624
>   Improve configure's recommendation message
>   https://trac.sagemath.org/ticket/30624
>  
> I don't have time to work on it now.
>

Update: I pushed a branch. Needs review. 

-- 
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 discussion on the web visit 
https://groups.google.com/d/msgid/sage-release/e4b79007-5aaf-49c3-97e5-65d2ae23116fo%40googlegroups.com.

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

[Samuel Lelievre]

Le lundi 21 septembre 2020 04:40:57 UTC+2, Matthias Köppe a écrit :
>
> On Wednesday, September 16, 2020 at 10:05:59 AM UTC-7 Samuel Lelievre 
> wrote:
>
>> [...]  what we should do about it is probably adapt the wording
>> to better convey that. For instance:
>>
>> hint: installing the following system packages, if not already
>> present, is recommended and may avoid building some SPKGs from
>> source (though some may have to be built anyway):
>> [...]
>>
>
> +1, ticket please
>

This is now:

- Sage Trac ticket 30624
  Improve configure's recommendation message
  https://trac.sagemath.org/ticket/30624
 
I don't have time to work on it now.

-- 
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 discussion on the web visit 
https://groups.google.com/d/msgid/sage-release/7c258b34-24f4-4c8c-b9b5-62e510e24313o%40googlegroups.com.

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

[Samuel Lelievre]

2020-09-16 09:51:38 UTC, Eric Gourgoulhon:
>
> On Ubuntu 20.04 running on Intel Core i7-8665U + 32 GB RAM:
>
> - build (-j8) from a fresh git clone with a maximum of system
>   packages (details below), including the system Python (3.8.2): OK
> - all tests from ptestlong passed
>
> Details of build:
> As recommended in [...]
> the following Ubuntu 20.04 packages were installed before the build:
>
> sudo apt-get install [...]
>
> Then, after running
>
> make configure
> ./configure
>
> I've installed [...] as recommended in the outcome of configure:
>
> sudo apt-get install [...]
>
> I then ran
>
> ./config.status --recheck && ./config.status
>
> which yielded the following recommendation:
>
> configure: hint: installing the following system packages
> is recommended and may avoid building some of the above SPKGs
> from source:
> configure:   $ sudo apt-get update
>   $ sudo apt-get install libcdd-dev libcdd-tools libnauty-dev
>
> However these packages are already installed in the system:

Recommendations of packages to install can still be improved,
see the dedicated ticket:

  https://trac.sagemath.org/ticket/29586

but we need to balance the maintenance effort with the gains.

In this case, what you can conclude is:

- satisfactory versions of these packages (or possibly packages
  that depend on them) for that OS were not found
- on some version of that OS, satisfactory versions of these
  packages exist that would avoid having to build them

and what we should do about it is probably adapt the wording
to better convey that. For instance:

hint: installing the following system packages, if not already
present, is recommended and may avoid building some SPKGs from
source (though some may have to be built anyway):
[...]

-- 
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 discussion on the web visit 
https://groups.google.com/d/msgid/sage-release/34216f32-0ee9-42da-a74b-c1d84510d2ebo%40googlegroups.com.

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

[Samuel Lelievre]

2020-09-11 22:31:21 UTC, Dima Pasechnik:
>
> On Fri, Sep 11, 2020 at 11:16 PM Samuel Lelievre:
>>
>> I'll reinstall gcc@9 and python@3.7 and  try again.
>
> but why, install gcc (i.g. gcc@10), Sage now accepts it.
> Probably you want to configure with CC=clang CXX=clang++
>
> You may also try installing python3.8 and use it
> with the experimental branch from
> https://trac.sagemath.org/ticket/30546

Can "git trac try" take several ticket numbers so as
to apply them both on top of the latest develop?
For instance will this work?

$ git trac try 30536 30546

Otherwise hopefully the next beta includes
at least 30536 which has positive review.

-- 
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 discussion on the web visit 
https://groups.google.com/d/msgid/sage-release/4efba0c6-1a2d-4db0-83d4-a216b322ff8co%40googlegroups.com.

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

[Samuel Lelievre]

Le vendredi 11 septembre 2020 05:55:47 UTC+2, Samuel Lelievre a écrit :
>
>
>
> Le jeudi 10 septembre 2020 19:15:43 UTC+2, Matthias Köppe a écrit :
>>
>> On Thursday, September 10, 2020 at 10:08:32 AM UTC-7, Samuel Lelievre 
>> wrote:
>>>
>>> On a MacBook Air (early 2014) with 
>>> macOS 10.14.6 Mojave, with Homebrew 
>>> (but having removed Homebrew packages 
>>> gcc@9, python@3.7, arb, flint, gap, singular), 
>>> `make` succeeds but `make testlong` fails 
>>> unexpectedly still referring to python@3.7. 
>>>
>>
>> "make distclean" and rebuilding should fix this
>>
>
> I forgot to mention this was a fresh git clone.
> I still tried your suggestion but testing failures
> persist after "make distclean" and rebuilding.
>

I'll reinstall gcc@9 and python@3.7 and  try again.

-- 
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 discussion on the web visit 
https://groups.google.com/d/msgid/sage-release/43d187fc-34aa-409d-bde2-caef240e5860o%40googlegroups.com.

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

[Samuel Lelievre]

Le jeudi 10 septembre 2020 19:15:43 UTC+2, Matthias Köppe a écrit :
>
> On Thursday, September 10, 2020 at 10:08:32 AM UTC-7, Samuel Lelievre 
> wrote:
>>
>> On a MacBook Air (early 2014) with 
>> macOS 10.14.6 Mojave, with Homebrew 
>> (but having removed Homebrew packages 
>> gcc@9, python@3.7, arb, flint, gap, singular), 
>> `make` succeeds but `make testlong` fails 
>> unexpectedly still referring to python@3.7. 
>>
>
> "make distclean" and rebuilding should fix this
>

I forgot to mention this was a fresh git clone.
I still tried your suggestion but testing failures
persist after "make distclean" and rebuilding.

-- 
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 discussion on the web visit 
https://groups.google.com/d/msgid/sage-release/a47beff6-d600-4f9b-afce-5c65cebb46ddo%40googlegroups.com.

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

[Samuel Lelievre]

2020-08-19 12:43:58 UTC, Sébastien Labbé:
>
> Testing with various optional and external packages, I get:
> [...]
>
 
Speaking of optional packages, could someone review

- Sage Trac ticket 30390: Fix PyPI url
  https://trac.sagemath.org/ticket/30390

-- 
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 discussion on the web visit 
https://groups.google.com/d/msgid/sage-release/9b271518-aa39-4ca4-bd24-2ddc7a676955o%40googlegroups.com.

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

[Samuel Lelievre]

2020-08-13 21:59:31 UTC, Dima Pasechnik:
>
> OK, I tried to reproduce this on a Mac, and indeed the build hangs 
> waiting for some parallel process to finish: 
> On hitting ctrl-C, it always (the stage of the docbuild may differ though) 
> shows the following backtrace: 
> ... 
> [dochtml] KeyboardInterrupt 
>

The hang occurs even with `make -j1`.

-- 
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 discussion on the web visit 
https://groups.google.com/d/msgid/sage-release/06455f10-9dd7-435d-8f7e-17f22c0f8cbco%40googlegroups.com.

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

[Samuel Lelievre]

I opened a ticket for the issue reported by John:

- Fix building html documentation on macOS
  https://trac.sagemath.org/ticket/30351

I tried applying #30345 but the problem persisted.
Then I realised Dima mentioned #30345 in relation to
timeouts when running make testalllong on Debian,
not in relation to the dochtml issue on macOS.  : /

-- 
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 discussion on the web visit 
https://groups.google.com/d/msgid/sage-release/1f862531-f68a-4554-9577-3c3f4cdc4abdo%40googlegroups.com.

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

[Samuel Lelievre]

2020-07-29 08:39:13 UTC, François Bissey:
>
> The important bits from that last log
> [198/517] creating build/[...]/build/cythonized/sage/libs/arb
> [...]
> In file included from build/cythonized/sage/libs/arb/arith.c:656:
> In file included from build/cythonized/sage/libs/arb/arb_wrap.h:14:
> In file included from /opt/s/sage92b6/local/include/acb.h:22:
> In file included from /opt/s/sage92b6/local/include/arf.h:27:
> In file included from /opt/s/sage92b6/local/include/fmpr.h:26:
> /opt/s/sage92b6/local/include/fmpz_extras.h:47:1:
> error: redefinition of 'fmpz_add_si'
> fmpz_add_si(fmpz_t z, const fmpz_t x, slong y)
> /usr/local/include/flint/fmpz.h:479:18:
> note: previous definition is here
> FMPZ_INLINE void fmpz_add_si(fmpz_t f, const fmpz_t g, slong x)
> In file included from build/cythonized/sage/libs/arb/arith.c:656:
> In file included from build/cythonized/sage/libs/arb/arb_wrap.h:14:
> In file included from /opt/s/sage92b6/local/include/acb.h:22:
> In file included from /opt/s/sage92b6/local/include/arf.h:27:
> In file included from /opt/s/sage92b6/local/include/fmpr.h:26:
> /opt/s/sage92b6/local/include/fmpz_extras.h:56:1:
> error: redefinition of 'fmpz_sub_si'
> fmpz_sub_si(fmpz_t z, const fmpz_t x, slong y)
> /usr/local/include/flint/fmpz.h:487:18:
> note: previous definition is here
> FMPZ_INLINE void fmpz_sub_si(fmpz_t f, const fmpz_t g, slong x)
> 2 errors generated.
>
> I would be easier to spot if you were building sagely at j1.

Thanks for digging through and thanks for the reminder that
building with one job produces easier to analyze logs.

I built again with `-j1`, here are the logs.

https://www.math.u-psud.fr/~lelievre/sagelogs
slel-sage-9-2-b6-mac-brew-2020-07-29-fail.zip

The errors seem to involve Flint. I have Flint 2.6.1 from Homebrew.

By the way, the upgrade to Flint 2.6.1 for Sage needs review at

  upgrade to flint 2.6.1
  https://trac.sagemath.org/ticket/29719

Should I
- uninstall Homebrew's flint and try again?
- downgrade Homebrew's Flint to 2.6.0 and try again?
- wait for the upgrade to Flint 2.6.1 to get merged in Sage?

-- 
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 discussion on the web visit 
https://groups.google.com/d/msgid/sage-release/edecd013-a6d9-4576-bd5d-c93a923ef705o%40googlegroups.com.

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

[Samuel Lelievre]

2020-07-26 20:46:10 UTC, Matthias Köppe:
>
> From your log:
>
> [  4/517] clang -Wno-unused-result [...]
> -I/opt/s/sage92b6/local/include/singular
> -I/opt/s/sage92b6/local/include/ -std=c++11
> In file included from [...]/letterplace_ideal.cpp:675:
> /usr/local/include/singular/Singular/libsingular.h:15:10:
> fatal error: 'polys/shiftop.h' file not found
> #include "polys/shiftop.h"
> ^
> In file included from [...]/free_algebra_letterplace.cpp:675:
> /usr/local/include/singular/Singular/libsingular.h:15:10:
> fatal error: 'polys/shiftop.h' file not found
> #include "polys/shiftop.h"
>  ^
> In file included from [...]/free_algebra_element_letterplace.cpp:675:
> /usr/local/include/singular/Singular/libsingular.h:15:10:
> fatal error: 'polys/shiftop.h' file not found
> #include "polys/shiftop.h"
>  ^
> [...]/finite_dimensional_algebra_element.c:11104:18:
> warning: unused function
> '__pyx_pw_4sage_9structure_7element_1parent' [-Wunused-function]
> static PyObject
> *__pyx_pw_4sage_9structure_7element_1parent(PyObject *__pyx_self,
> PyObject *__pyx_v_x) {
>
> This appears to be a conflict with a version of Singular
> that is installed in /usr/local


2020-07-26 22:01:03 UTC, Matthias Köppe:
>
> This will be addressed in
> https://trac.sagemath.org/ticket/30227


2020-07-28 04:13:48 UTC, Matthias Köppe:
>
> Fixed in #30227, please test


Dear Matthias, thanks for investigating and for the ticket.

I uninstalled Homebrew's Singular: new failure on sagelib.

https://www.math.u-psud.fr/~lelievre/sagelogs/slel-sage-9-2-b6-mac-brew-2020-07-27-fail.zip

I then tried applying ticket 30227, new failure on sagelib.

https://www.math.u-psud.fr/~lelievre/sagelogs/
slel-sage-9-2-b6-mac-brew-2020-07-28.zip

-- 
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 discussion on the web visit 
https://groups.google.com/d/msgid/sage-release/dbc12617-0a8f-4104-a016-a24a4e64bc50o%40googlegroups.com.

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

[Samuel Lelievre]

2020-07-08 07:14:54 UTC, Eric Gourgoulhon:
>
> 2020-07-07 22:56:55 UTC, Justin C. Walker:
>>
>>
>> So today, I dutifully did the same thing (for beta3). However,
>> once getting the repository in place, there was no “./configure”.
>
> You should run
>
> make configure
>
> first. In other words, the full build process from scratch is
>
> git clone https://github.com/sagemath/sage.git
> cd sage
> make configure
> ./configure
> MAKE="make -j8" make
>

On macOS there's one extra step if you have Homebrew:

URL='https://github.com/sagemath/sage.git'
git clone $URL
cd sage
. ./.homebrew-build-env
make configure
./configure
make

-- 
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 discussion on the web visit 
https://groups.google.com/d/msgid/sage-release/42b6eb2a-d692-498f-a18f-1c80d39a54cdo%40googlegroups.com.

Re: [sage-release] Re: Sage 9.1.beta1 released (fplll on ARM problem?)

[Samuel Lelievre]

2020-01-26 18:37:59 UTC, Martin Albrecht:
>
> Sorry, I have no idea about this. But indeed, we never test on ARM. 
> Feel free to open an issue on FPLLL’s issue tracker but I’m not sure
> there’s much we can do without a machine to test things on.

I opened this issue:

  https://github.com/fplll/fplll/issues/432

It might be possible to use GitHub actions to test on ARM.

-- 
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 discussion on the web visit 
https://groups.google.com/d/msgid/sage-release/e8b01657-bf45-4f46-b148-909fbc305aa6o%40googlegroups.com.

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

[Samuel Lelievre]

Wed 2020-05-06 19:35:12 UTC, Jonathan Kliem:
>
> Thank you Samuel Lelievre and Emmanuel Charpentier
> for testing. Your doctests failures are known:
>
> If pari 2.11.4 is installed on the system



> If you use glpk from your system,



> If you have libsqlite3 but not sqlite3 installed,



> I think none of those failures is serious enough that
> it needs to be handled now. We also need to make a
> general decision on how we deal with doctests that
> may vary slighly by the system package and how rigid
> we are with accepting system packages (is the glpk
> "bug" already serious enough to reject it).

Thanks Jonathan for the explanation of these points.
That helped. Got sqlite3 installed on the Debian 9
system and that got tests to pass for Sage 9.1.rc4.

-- 
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 discussion on the web visit 
https://groups.google.com/d/msgid/sage-release/411a5ffe-3401-449f-9db3-429a1356d044%40googlegroups.com.

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

[Samuel Lelievre]

Le samedi 25 avril 2020 18:15:55 UTC+2, Matthias Köppe a écrit :
>
> On Saturday, April 25, 2020 at 9:02:42 AM UTC-7, Samuel Lelievre wrote:
>>
>>
>> 1. The 'configure' step suggested to `brew install ppl`
>> even though I already had Homebrew's ppl. [...]
>> So the decision to install ppl was based on that, 
>> not on the absence of ppl. In such a case, maybe 
>> the script should not recommend installing ppl 
>> (at least not without checking if it is there). 
>>
>
> I collect wishlist items for this code at 
> https://trac.sagemath.org/ticket/29146
> ("Meta-ticket: Refactor system package related scripts, tox.ini, 
> build/bin/write_dockerfile.sh")
>
> You can add your suggestion there. Won't happen for 9.1.
>

Opened

- Sage Trac ticket #29586
  Improve configure's recommendations
  https://trac.sagemath.org/ticket/29586

with milestone 9.2 and was adding it to #29146
but you beat me to it.

-- 
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 discussion on the web visit 
https://groups.google.com/d/msgid/sage-release/1e8809fa-093c-4d78-93e7-05f926f73b8e%40googlegroups.com.

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

[Samuel Lelievre]

> Date: Wed 2020-04-22 22:41:50 UTC
> From: Volker Braun
> Subject: Sage 9.1.rc1 released

Thanks for this new development release.

On macOS 10.14.6 Mojave with lots of Homebrew
packages installed, failed to build Pillow. Logs:

https://www.math.u-psud.fr/~lelievre/t/sage3logs.zip

-- 
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 discussion on the web visit 
https://groups.google.com/d/msgid/sage-release/90d822a1-46bf-4642-b4af-29dd84502729%40googlegroups.com.

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

[Samuel Lelievre]

Le lundi 13 avril 2020 17:35:58 UTC+2, Matthias Köppe a écrit :
>
> On Sunday, April 12, 2020 at 3:37:55 PM UTC-7, 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 
>>
>> 10ed24e3ed (trac/develop, tag: 9.1.rc0) Updated SageMath version to 
>> 9.1.rc0
>>
>
> If you are testing on macOS, I recommend to merge #29404 and #29408
>
which missed the 9.1.rc0 bus and fix critical failures observed in 
> 9.1.beta9.
>

Can you say how to merge #29404 and #29408
on top of 9.1.rc0 to get things to work in macOS?

I am on macOS 10.14.6 and I have not been able
to build a single version of Sage after 9.0.

-- 
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 discussion on the web visit 
https://groups.google.com/d/msgid/sage-release/c1680db4-0fc1-4004-86e5-de309894eb9c%40googlegroups.com.

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

[Samuel Lelievre]

This is now Sage Trac ticket 28928:

  https://trac.sagemath.org/ticket/28928

Le lundi 30 décembre 2019 12:00:07 UTC-5, Simon King a écrit :
>
> Hi Samuel,
>
> did you open a ticket for the problem in sageinspect?
>
> Best regards,
> Simon
>
> On Saturday, December 28, 2019 at 8:12:31 AM UTC+1, Samuel Lelievre wrote:
>>
>> Thu 2019-12-26 à 23:24 UTC, Volker Braun: 
>> > 
>> > 746a826377 (trac/develop, tag: 9.0.rc0) Updated SageMath version to 
>> 9.0.rc0 
>>
>>
>> Computer, OS, build choices: 
>>
>> - iMac, Mid 2015 
>> - macOS 10.14.6 Mojave 
>> - build for Python 2 
>> - build Sage's `gcc` and `openssl` packages 
>> - build Sage's Python with its `_ssl` and `_tkinter` modules 
>>
>> Running `make testlong` gave 2 failing doctests 
>> in the file `src/sage/misc/sageinspect.py`. 
>>
>> Running the tests for that file again gave 6 failing doctests. 
>>
>> Excerpts from the terminal session follow. 
>>
>>
>> ```bash 
>> $ make testlong 
>>
>> [...] 
>>
>> -- 
>> sage -t --long --warn-long 50.2 src/sage/misc/sageinspect.py  # 2 
>> doctests failed 
>> -- 
>> Total time for all tests: 11201.1 seconds 
>> cpu time: 8574.9 seconds 
>> cumulative wall time: 10884.3 seconds 
>> make: *** [testlong] Error 1 
>> ``` 
>>
>>
>> ```bash 
>> $ ./sage -t --long --warn-long 50.2 src/sage/misc/sageinspect.py 
>> Running doctests with ID 2019-12-27-15-55-47-4a6bf556. 
>> Git branch: develop 
>> Using --optional=build,dochtml,mpir,python2,sage 
>> Doctesting 1 file. 
>> sage -t --long --warn-long 50.2 src/sage/misc/sageinspect.py 
>> ** 
>> File "src/sage/misc/sageinspect.py", line 2132, in 
>> sage.misc.sageinspect._sage_getsourcelines_name_with_dot 
>> Failed example: 
>> cython(''' 
>> class A: 
>> def __init__(self): 
>> "some init doc" 
>> pass 
>> class B: 
>> "some class doc" 
>> class A(A): 
>> pass 
>> ''') 
>> Exception raised: 
>> Traceback (most recent call last): 
>>   File 
>> "/Users/lelievre/s/sage2gcc/local/lib/python3.7/site-packages/sage/doctest/forker.py",
>>  
>>
>> line 681, in _run 
>> self.compile_and_execute(example, compiler, test.globs) 
>>   File 
>> "/Users/lelievre/s/sage2gcc/local/lib/python3.7/site-packages/sage/doctest/forker.py",
>>  
>>
>> line 1123, in compile_and_execute 
>> exec(compiled, globs) 
>>   File "> sage.misc.sageinspect._sage_getsourcelines_name_with_dot[3]>", line 
>> 10, in  
>> ''') 
>>   File "sage/misc/lazy_import.pyx", line 353, in 
>> sage.misc.lazy_import.LazyImport.__call__ 
>> (build/cythonized/sage/misc/lazy_import.c:3686) 
>> return self.get_object()(*args, **kwds) 
>>   File 
>> "/Users/lelievre/s/sage2gcc/local/lib/python3.7/site-packages/sage/misc/cython.py",
>>  
>>
>> line 634, in cython_compile 
>> return cython_import_all(tmpfile, get_globals(), **kwds) 
>>   File 
>> "/Users/lelievre/s/sage2gcc/local/lib/python3.7/site-packages/sage/misc/cython.py",
>>  
>>
>> line 524, in cython_import_all 
>> m = cython_import(filename, **kwds) 
>>   File 
>> "/Users/lelievre/s/sage2gcc/local/lib/python3.7/site-packages/sage/misc/cython.py",
>>  
>>
>> line 504, in cython_import 
>> return builtins.__import__(name) 
>> ModuleNotFoundError: No module named 
>> '_Users_lelievre__sage_temp_Ghost_80496_tmp_2caqjln__pyx_0' 
>> ** 
>> File "src/sage/misc/sageinspect.py", line 2142, in 
>> sage.misc.sageinspect._sage_getsourcelines_name_with_dot 
>> Failed example: 
>> B.A.__name__ 
>> Exception raised: 
>> Traceback (most recent call last): 
>>   File 
>> "/Users/lelievre/s/sage2gcc/local/lib/python3.7/site-packages/sage/doctest/forker.py",
>>  
>>
>> line 681, in _run 
>> self.compile_and_execute(example, compiler, test.globs) 
>>   File 
>> "/Users/lelievre/s/sage2gcc

[sage-release] Re: [sage-support] Changelog for Sage?

[Samuel Lelievre]

So far Jeroen was taking care of this after each release.
It's a matter of running a script and checking that there
are no typos in author names and reviewer names.
Would anyone want to relieve him of that responsibility?


Thu 2019-10-17 13:32:49 UTC, Dima Pasechnik:
>
> any idea why no release notices have been created after 8.7 ? 
>
> -- Forwarded message - 
> From: Szabolcs Horvát > 
> Date: Thu, Oct 17, 2019 at 11:59 AM 
> Subject: [sage-support] Changelog for Sage? 
> To: sage-support > 
>
>
> Is there a changelog for Sage 8.8 or 8.9? I can only find 8.7 on the 
> website: http://www.sagemath.org/changelogs/index.html 
>
> Are there plans to create a more user-friendly changelog? The 
> changelogs I linked list every single change, but it is hard for a 
> normal user (not a developer) to figure out if there was a change that 
> is relevant for me ... Many other software have both a full list of 
> changes, but also an easy to digest summary of important major 
> changes. 
>
>

-- 
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 discussion on the web visit 
https://groups.google.com/d/msgid/sage-release/838907eb-dc61-41b5-a3ea-9e8c5ccc5fc4%40googlegroups.com.

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

[Samuel Lelievre]

Sun 2019-10-19 22:33:17 UTC, Volker Braun:
>
> 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 
>

>
> 76b7fdd115 (tag: 9.0.beta2, trac/develop) Updated SageMath version to 
> 9.0.beta2
>
 
Thanks for this new release!

I'm at the "Illustrating Mathematics" ICERM program,
trying to help as many people as I can to install Sage
and get started using it.

Fresh install (from develop source tarball)
on a MacBook Air with macOS 10.12.6
failed while trying to build Singular.

Log files:

https://www.math.u-psud.fr/~lelievre/sagelogs/sage-9.0.beta2-ed/config.log.txt
https://www.math.u-psud.fr/~lelievre/sagelogs/sage-9.0.beta2-ed/singular-4.1.1p2.p0.log.txt

-- 
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 discussion on the web visit 
https://groups.google.com/d/msgid/sage-release/74452ec1-1d6f-48ec-baf8-50831eb19015%40googlegroups.com.

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

[Samuel Lelievre]

Le mardi 27 août 2019 22:04:42 UTC+2, Sébastien Labbé a écrit :
>
>
> I reinstalled my openssl which looks recent:
>
> (sage-sh) $ openssl version
> OpenSSL 1.1.1b  26 Feb 2019
>
> But this does not fix the issue.
>

After installing openssl, you need to force-reinstall python.

sage -f python2
sage -f python3

so that their ssl module gets compiled, taking into account
the (new) presence of OpenSSL.


-- 
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 discussion on the web visit 
https://groups.google.com/d/msgid/sage-release/9b8bde5f-eadb-4317-bdb9-13c53404a698%40googlegroups.com.

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

[Samuel Lelievre]

Also, pdf chapters of the SageMath documentation tend
to rank quite high among results for web search engine
queries about Sage.

-- 
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 this group, send email to sage-release@googlegroups.com.
Visit this group at https://groups.google.com/group/sage-release.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/sage-release/b6d52ac4-51b6-4368-91ad-32ede451c16b%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

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

[Samuel Lelievre]

Sat 2019-06-01 06:29:44 UTC, Dima Pasechnik:
>
> On Sat, Jun 1, 2019 at 7:25 AM Frédéric Chapoton:
> > 
> > Do we plan to distribute also a python3-version of 
> > sage 8.8 (binaries) ? Of course, some tests are still
> > not passing, but sage works nevertheless.
>
> IMHO it is too early. 
> Some parts of python3 version produce patently incorrect results, e.g. 
> graph automorphisms/isomorphisms. 
> It would not be a good idea to distribute such a binary without big 
> warnings printed to that effect. 

Then how about distributing it with big warnings.

There is Python 3 impatience in part of Sage's user base.
Distributing an experimental Python 3 version would send
a good signal.

We could call the binaries "SageMath-py3-experimental"
and include a big warning in the banner, with a link to the
"Migration to Python 3" page on the Sage wiki.

-- 
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 this group, send email to sage-release@googlegroups.com.
Visit this group at https://groups.google.com/group/sage-release.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/sage-release/8beed8fe-cc20-4cf3-8a54-77973b2d661c%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

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

[Samuel Lelievre]

Mon 2018-11-26 03:21:58 UTC+1, Steven Trogdon:
>
> Something rather weird here. I'm unable to complete a pull of the latest 
> 8.5.beta5 because of
>
> Updating f894105d0d..b36eca1990
> error: unable to unlink old 'docker/entrypoint.sh': Permission denied
>
> Now entrypoint.sh is owned by root which I find strange
>
> ls -al docker/entrypoint.sh
> -rwxr-xr-x 1 root root 315 Aug 26 12:46 docker/entrypoint.sh
>
> In fact in SAGE_ROOT there are numerous folders and a file owned by root
>
> ls -al | grep 'root '
> drwxr-xr-x  2 root root   4096 Aug 26 12:46 .ci
> drwxr-xr-x  2 root root   4096 Aug 26 12:46 .circleci
> lrwxrwxrwx  1 root root 10 Aug 26 12:46 .dockerignore -> .gitignore
> -rw-r--r--  1 root root   6753 Aug 26 12:46 .gitlab-ci.yml
> drwxr-xr-x  3 root root   4096 Aug 26 12:46 docker
>
> Any idea as to what's with this? 8.5.beta4 was just fine.
>

I don't see anything like that here.
Did you maybe perform a "git pull" as root at some point?

-- 
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 this group, send email to sage-release@googlegroups.com.
Visit this group at https://groups.google.com/group/sage-release.
For more options, visit https://groups.google.com/d/optout.

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

[Samuel Lelievre]

Tue 2018-11-20 11:45:15 UTC+1, Martin R:
> The findstat doctest is a trivial fix (remove the first useless ellipsis),
> if you open a ticket, I'll fix it immediately.

Ticket at: https://trac.sagemath.org/ticket/26728

-- 
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 this group, send email to sage-release@googlegroups.com.
Visit this group at https://groups.google.com/group/sage-release.
For more options, visit https://groups.google.com/d/optout.

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

[Samuel Lelievre]

Thu 2018-10-04, 11:12:29 UTC+2, Erik Bray:
>
> Sometimes when I run the tests I get failures like:
>
> sage -t --long src/sage/combinat/cluster_algebra_quiver/quiver.py
> **
> File "src/sage/combinat/cluster_algebra_quiver/quiver.py", line 172,
> in sage.combinat.cluster_algebra_quiver.quiver.ClusterQuiver
> Failed example:
> Q.mutation_type()
> Exception raised:
> Traceback (most recent call last):
> ... 
> ValueError: unsupported pickle protocol: 3
>
> This is because I'm using the same machine to build and test Python 3,
> and that code is caching some computations as pickles in .sage/; so
> when I run them on Python 3 it ends up with some Python 3 pickles in
> .sage.
>
> I believe these tests ought to be fixed to not use the user's real
> .sage since that's hard to control for.  But that's a minor issue and
> not particular to this release.  It just gets me almost every time :)

This is now tracked at:

  https://trac.sagemath.org/ticket/26409

-- 
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 this group, send email to sage-release@googlegroups.com.
Visit this group at https://groups.google.com/group/sage-release.
For more options, visit https://groups.google.com/d/optout.

[sage-release] Re: sage-8.4

[Samuel Lelievre]

Le mardi 7 août 2018 07:56:41 UTC+2, HG a écrit :
>
>
> I have an old computer intel dual core with 4 Go RAM, I have cosmic 
> (ubuntu +1 =18.10) installed and I tried compiling the sage 8.4 version, 
> no problem after a night compilation... ok. 
>

Hi Henri, thanks for the information. To clarify, your post is about
Sage 8.4.beta0, not Sage 8.4. Also, in the future please post such
information as a reply to the release announcement, rather than
as a separate post on sage-release.
Best, Samuel 

-- 
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 this group, send email to sage-release@googlegroups.com.
Visit this group at https://groups.google.com/group/sage-release.
For more options, visit https://groups.google.com/d/optout.

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

[Samuel Lelievre]

Under macOS 10.10.5, after downloading the cysignals patch

https://github.com/sagemath/cysignals
/commit/daef81e2fc111378ccc58b3f572eb18c70753a30.patch

into

build/pkgs/cysignals/patches

both the build+docbuild of Python2-based Sage
and the build+nodocbuild of Python3-based Sage
were successful. I have not run the tests.

-- 
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 this group, send email to sage-release@googlegroups.com.
Visit this group at https://groups.google.com/group/sage-release.
For more options, visit https://groups.google.com/d/optout.

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

[Samuel Lelievre]

Mon 2017-12-17 20:06:46 UTC, Justin C. Walker:
>
> Built w/o problems from fresh clone/pull of “develop” branch,
> on macOS 10.11.6 (Quad-core Core i7). 
>
> Testing (‘ptestlong’) yielded two failures that persisted when run by 
itself.
> Later, I tried this “by hand” (copying the sage commands near these
> failures and pasting into a sage (8.1-b2) session, and they all passed.
>
> Not sure what that means. 
>
> Justin 
>
> ===Test results from original run=== 
>
> Running doctests with ID 2017-12-23-16-13-42-53923fd7. 
> Git branch: develop 
> Using --optional=mpir,python2,sage 
> Doctesting 1 file. 
> sage -t --warn-long 78.1 src/sage/combinat/matrices/dancing_links.pyx 
> ** 
> File "src/sage/combinat/matrices/dancing_links.pyx", line 27, in 
sage.combinat.matrices.dancing_links 
> Failed example: 
> sorted(x.one_solution(ncpus=8)) 
> Expected: 
> [0, 1] 
> Got: 
> [2, 3] 
> ** 
> File "src/sage/combinat/matrices/dancing_links.pyx", line 524, in 
sage.combinat.matrices.dancing_links.dancing_linksWrapper.one_solution 
> Failed example: 
> sorted(d.one_solution(ncpus=8)) 
> Expected: 
> [0, 1] 
> Got: 
> [2, 3] 
> ** 


Fixed here:
https://trac.sagemath.org/ticket/24424 

-- 
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 this group, send email to sage-release@googlegroups.com.
Visit this group at https://groups.google.com/group/sage-release.
For more options, visit https://groups.google.com/d/optout.

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

[Samuel Lelievre]

Le samedi 4 février 2017 14:41:49 UTC+1, Volker Braun a écrit :
>
> On Saturday, February 4, 2017 at 11:55:00 AM UTC+1, Samuel Lelievre wrote:
>>
>> Should 'make ptestlong' ignore the content of 'init.sage'?
>>
>
> Yes. 
>

Note that there is a ticket for that:

#20270 some doctests are influenced by the contents of init.sage 
https://trac.sagemath.org/ticket/20270

-- 
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 this group, send email to sage-release@googlegroups.com.
Visit this group at https://groups.google.com/group/sage-release.
For more options, visit https://groups.google.com/d/optout.

[sage-release] Re: Conda package for Sage

[Samuel Lelievre]

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 sage-spkg-sources -c isuruf -c conda-forge
>
> This was a hacky build and I don't expect everything to work properly. 
sage command, sage notebook, gap, maxima and a few packages I've checked 
works.
>
> There were 86 standard packages in conda-forge and default channel. 
(conda-forge is a community effort, see https://conda-forge.github.io/). 
These conda packages were used instead of sage's packages
>
> 74 standard packages were built in the docker container 
condaforge/linux-anvil with SAGE_FAT_BINARY=yes, which should make the 
packages compatible with distros as old as CentOS 6. I used sage's build 
process to create these, kept track of which files were created and copied 
them over to a conda package.
>
> Things to note are,
> 1. anaconda.org r channel is incompatible with conda-forge. So rpy2 and r 
is not bundled, but conda-forge has started packaging the r packages.
> 2. only the SAGE_LOCAL folder is packaged. So no development.
> 3. sage-env is sourced when the env is activated, but the deactivation 
doesn't seem to work properly. Your shell session may become unusable.
> 4. pinning needs to happen so that ABI compatibility is there.
> 5. Packages are built with gmp.
> 6. miniconda2 has issues with path names having non-ASCII characters, so 
you have to use miniconda3 as your root environment.
>
> Anybody interested in making proper conda packages for the remaining 74 
packages and sage itself?
>
> Isuru Fernando

Hi Isuru Fernando,

Thanks for this packaging and for reporting to sage-devel.

I'm cc-ing sage-packaging and sage-release which are also
appropriate place to announce this.

I updated the "Distribution" wiki page at

https://wiki.sagemath.org/Distribution

Best, Samuel

-- 
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 this group, send email to sage-release@googlegroups.com.
Visit this group at https://groups.google.com/group/sage-release.
For more options, visit https://groups.google.com/d/optout.

[sage-release] Re: Reverting blacklisting of GCC 4.8 (#20231)

[Samuel Lelievre]

2016-05-13 11:15:02 UTC+2, Christian Stump:
>
> On Wednesday, May 11, 2016 at 9:35:35 PM UTC+2, Eric Gourgoulhon wrote:
>>
>> +1 for still supporting GCC 4.8 for a while (unless it's very 
>> troublesome): this is the GCC version of Ubuntu 14.04 LTS, which is 
>> officially supported until April 2019. 
>>
>
> +1. I indeed use 14.04 LTS and will do so until I can upgrade to 16.04 LTS 
> -- that will be happening in about 2-3 months from now.
>
> Christian
>

Support for GCC 4.8 was restored at #20594, merged in Sage 7.2.rc2.
http://trac.sagemath.org/ticket/20594


-- 
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 this group, send email to sage-release@googlegroups.com.
Visit this group at https://groups.google.com/group/sage-release.
For more options, visit https://groups.google.com/d/optout.

[sage-release] Re: Sage Fedora RPM

[Samuel Lelievre]

2016-02-04 23:30:12 Z, Volker Braun:
>
> I'm working automating distribution packaging with our binary builds. 
> There is now an experimental sage rpm package for Fedora 23 at 
>
> http://files.sagemath.org/linux/64bit/sagemath-7.1.beta1-1.x86_64.rpm
>
> The rpm installs to /opt/SageMath and doesn't add a link anywhere in the 
> path, so you need to run it using
>
> /opt/SageMath/sage
>
> This obviously needs to be improved upon, but apart from that it should 
> work just like the normal binary package (except install much faster since 
> there is no patching involved).
>

cc-ing Paulo César Pereira de Andrade, current
maintainer of the sagemath package for Fedora.

https://apps.fedoraproject.org/packages/sagemath

-- 
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 this group, send email to sage-release@googlegroups.com.
Visit this group at https://groups.google.com/group/sage-release.
For more options, visit https://groups.google.com/d/optout.

Re: [sage-release] Sage 7.0 released

[Samuel Lelievre]

2016-01-31 23:39:30 Z, Justin C. Walker:
>
>
> On Jan 31, 2016, at 15:23 , Volker Braun wrote: 
>
> > Is that a parallel build? the mashed-together log isn't very meaningful. 
>
> Yes it is (-j24; Dual 6-core Xeons). 
>
> With any luck, you will find a tarball of the logs directory attached. 
>
 
I think Volker's question could be expanded into the
following recommendation.

When a parallel build fails, it's good to
- save the log files
- run a non-parallel build.

If the non-parallel build also fails, it will provide
easier-to-analyze logs.

Otherwise, you can report that the failure was
observed with the parallel build but not with
the non-parallel build.

-- 
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 this group, send email to sage-release@googlegroups.com.
Visit this group at https://groups.google.com/group/sage-release.
For more options, visit https://groups.google.com/d/optout.

[sage-release] Re: Sage developers days on packaging, portability, documentation tools

[Samuel Lelievre]

The upcoming Sage developer days at Cernay on
packaging, portability, documentation tools
are now numbered "Sage Days 77".

https://wiki.sagemath.org/days77

The dates should be decided by next week-end,
it's still time to indicate your preferred dates at

https://framadate.org/HSPRcUBuWDFnSx95

You can also add content ideas and wishes at

https://wiki.sagemath.org/days77/projects


-- Forwarded message (very slightly edited) --
From: Nicolas M. Thiery 
Date: 2016-01-21 0:11 GMT+00:00
Subject: Sage developer days on packaging, portability, documentation tools

Dear Sage developers, ODK participants, ...

We will organize a week-long Sage developer days in the coming
months in Cernay, near Paris. Tentatively, the main themes will be:

- Sage packaging
- Sage on Windows
- Sage's documentation system (Sphinx)

If you are tentatively interested in participating, please fill in
the following poll to help us select an appropriate week:

https://framadate.org/HSPRcUBuWDFnSx95

We have funding for some developers with experience or specific
interest on the above themes. Please get in touch with me!

Cheers,
Nicolas


--
Nicolas M. Thiéry "Isil" 
http://Nicolas.Thiery.name/

-- 
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 this group, send email to sage-release@googlegroups.com.
Visit this group at https://groups.google.com/group/sage-release.
For more options, visit https://groups.google.com/d/optout.

Re: [sage-release] Re: Sage 7.0 virtual appliance

[Samuel Lelievre]

I think updating the instructions to use the SageAppliance on Windows
is an emergency. I remember reading that the Windows version is by far
the top download. It's annoying for users when things break.


-- 
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 this group, send email to sage-release@googlegroups.com.
Visit this group at https://groups.google.com/group/sage-release.
For more options, visit https://groups.google.com/d/optout.

[sage-release] Re: Sage-6.10.rc1 binaries test

[Samuel Lelievre]

Mon, 14 Dec 2015 15:43:54 -0800 (PST), Volker Braun:

> Here is a final test for the binaries, using the new
> binary packaging. That is, now binaries are patched
> automatically on first run, no more relocation after that.

Thank you for that.

On a MacBook Air running OS X 10.10.5, I downloaded

sage-6.10.rc1-OSX_10.11.2-x86_64.tar.bz2

from http://files.sagemath.org/binaries/ using Chrome.
The downloaded archive self extracted, producing
a folder called SageMath.

In the Finder, I renamed it SageMath-6.10.rc1 and
copied it to /opt (this required admin authentication).

Then I opened a Terminal and did

$ cd /opt/SageMath-6.10.rc1
$ ./sage

and everything seemed to work well.

Similarly

$ ./sage -n

worked well

I also tried

$ ./sage -n jupyter

which started the Jupyter notebook server,
and fired up a browser connecting to

http://localhost:/tree

>From there, I couldn't figure out how to navigate
to my home folder to create a jupyter notebook.

So I closed the browser window, and in Terminal
I typed Ctrl-C to stop the Jupyter notebook server,
then changed directory to my home and tried again:

$ cd ~
$ /opt/SageMath-6.10.rc1/sage -n jupyter

Then the Jupyter notebook server started, fired up
a browser connecting to it. I saw the listing of my
home folder. I navigated to some place and clicked
"New > SageMath 6.10.rc1", which created a new
Jupyter notebook and popped up the following alert:

Failed to retrieve MathJax from '/nbextensions/mathjax/MathJax.js'

Math/LaTeX rendering will be disabled.

If you have administrative access to the notebook server and a working 
internet connection, you can install a local copy of MathJax for offline 
use with the following command on the server at a Python or Jupyter prompt:

>>> from Jupyter.external import mathjax; mathjax.install_mathjax()

This will try to install MathJax into the Jupyter source directory.

If Jupyter is installed to a location that requires administrative 
privileges to write, you will need to make this call as an administrator, 
via 'sudo'.

When you start the notebook server, you can instruct it to disable 
MathJax support altogether:

$ ipython notebook --no-mathjax

which will prevent this dialog from appearing.

I clicked "OK" and gave the Jupyter notebook a try.
Most things work. Some don't.

- As expected given the above warning,
  maths in markdown cells doesn't work, for instance
  I changed the type of a cell to markdown and input

  The identity $a^2 - b^2 = (a - b)*(a + b)$ is remarkable.

   and it was displayed as is, latex was not rendered.

- plotting worked.

- something seems wrong with jmol, I input

  plot3d(lambda x, y: x*y, (-2, 2), (-2, 2))

  and this gives an output field that seems empty but long
  (the next input cell is pushed down quite a bit).

I'd love to hear explanations about any of the issues
I mentioned above. Some of the failures might have to
do with the SageMath 6.10.rc1 release while others
might have to do with the binary packaging, and some
might have to do with using OS X 10.11 binaries under
OS X 10.10.

Let me conclude by mentioning that I also downloaded
the SageMath 6.10.rc1 tarball and built Sage, I get other
issues which I'll report in the corresponding thread.

Best,
Samuel

-- 
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 this group, send email to sage-release@googlegroups.com.
Visit this group at https://groups.google.com/group/sage-release.
For more options, visit https://groups.google.com/d/optout.

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

[Samuel Lelievre]

2015-02-23 10:40:06 UTC+1, Dima Pasechnik:

 On 2015-02-23, John Cremona john.c...@gmail.com javascript: wrote: 
  On 22 February 2015 at 22:27, Volker Braun vbrau...@gmail.com 
 javascript: wrote: 
  Looks like your system git is incompatible with the Sage libcrypto and 
 the 
  dev scripts launch git without sage-native-execute. 
  
  THat would be quite serious -- this is a standard ubuntu 14.04 server 
  install, and the ubuntu git package is 1:1.9.1-1ubuntu0.1. 

 Given that the current git release is 2.3, this is old... 
 So the way would be to build Sage git spkg first thing. 

 Dima


Since a serious vulnerability was found in git in December 2014,
and quickly fixed, updating to a newer version of git is advisable.

-- 
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 this group, send email to sage-release@googlegroups.com.
Visit this group at http://groups.google.com/group/sage-release.
For more options, visit https://groups.google.com/d/optout.